Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 42a01a10e979ffcf45800807d9b4f16e2ce01a6ea34fe5d83e57c7f60a1024aa

Tx prefix hash: dd6837e9cd5c2c4b49e1bec40068f72baa26417be42f9056d58deb4282a41de7
Tx public key: 68ef4041c37844a4b2011d285ee57fd6d90fb2ca6c1cdde2b1806ab2eff228d6
Timestamp: 1773860093 Timestamp [UTC]: 2026-03-18 18:54:53 Age [y:d:h:m:s]: 00:241:00:47:25
Block: 1500675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177683 RingCT/type: yes/0
Extra: 0168ef4041c37844a4b2011d285ee57fd6d90fb2ca6c1cdde2b1806ab2eff228d6021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc757afdd74285751c9ed0edd16195974b83f5843b817eea39eb9463d540e183 0.000600000000 1990351 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1500685, "vin": [ { "gen": { "height": 1500675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc757afdd74285751c9ed0edd16195974b83f5843b817eea39eb9463d540e183" } } ], "extra": [ 1, 104, 239, 64, 65, 195, 120, 68, 164, 178, 1, 29, 40, 94, 229, 127, 214, 217, 15, 178, 202, 108, 28, 221, 226, 177, 128, 106, 178, 239, 242, 40, 214, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: