Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2db501b9a5b71a7633b77e4f3be85193d815d1ca415f6b592716b43b94d95404

Tx prefix hash: cfc39a377cf4a23856b3049547ead5b37e427c1477bd939b2216c19a6b427ca7
Tx public key: 0d0f4caa352dfde188dc73687143c6052dbe8113b8b59908f2c01d0a17b48466
Timestamp: 1743831317 Timestamp [UTC]: 2025-04-05 05:35:17 Age [y:d:h:m:s]: 01:227:10:58:03
Block: 1254633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426613 RingCT/type: yes/0
Extra: 010d0f4caa352dfde188dc73687143c6052dbe8113b8b59908f2c01d0a17b484660211000000014060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d6d73e12d2fca9dd2dd35f59b2dc249549702e8e240d11e3a61fe46050630887 0.000600000000 1741714 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": 1254643, "vin": [ { "gen": { "height": 1254633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6d73e12d2fca9dd2dd35f59b2dc249549702e8e240d11e3a61fe46050630887" } } ], "extra": [ 1, 13, 15, 76, 170, 53, 45, 253, 225, 136, 220, 115, 104, 113, 67, 198, 5, 45, 190, 129, 19, 184, 181, 153, 8, 242, 192, 29, 10, 23, 180, 132, 102, 2, 17, 0, 0, 0, 1, 64, 96, 246, 210, 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: