Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd2bf36716ce6d8110fd9126d14173752489dfd90d93ceab875ab38fc17e91e2

Tx prefix hash: bb306b5173bcf1b05d72583787d5e57f867c8c39be5a8656ec3c2674594a6105
Tx public key: ccd8471fe5cdc3b128bcb4e927de41ec13234313d4042c3775dc5a53c0e07314
Timestamp: 1773373705 Timestamp [UTC]: 2026-03-13 03:48:25 Age [y:d:h:m:s]: 00:249:12:39:48
Block: 1496680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183813 RingCT/type: yes/0
Extra: 01ccd8471fe5cdc3b128bcb4e927de41ec13234313d4042c3775dc5a53c0e07314021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 92d0b07697bf5692a8f5e1a80b29102dda1796e46fb0c06e9ebeaf1542abae1e 0.000600000000 1986306 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": 1496690, "vin": [ { "gen": { "height": 1496680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92d0b07697bf5692a8f5e1a80b29102dda1796e46fb0c06e9ebeaf1542abae1e" } } ], "extra": [ 1, 204, 216, 71, 31, 229, 205, 195, 177, 40, 188, 180, 233, 39, 222, 65, 236, 19, 35, 67, 19, 212, 4, 44, 55, 117, 220, 90, 83, 192, 224, 115, 20, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: