Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b37bd5e53131ecdf9ea1f17dc06ecea8c6318019998065ca9558eac8e1469c

Tx prefix hash: 3f9186a9e8d9d5d411027fca2781fed859ebc57b5efb768b8c2e0ec72ea1225e
Tx public key: 0f64d7fe9a78bf0f83fd0f2ec4d225949fbf20584290399d6876dea76e60e1d4
Timestamp: 1755439483 Timestamp [UCT]: 2025-08-17 14:04:43 Age [y:d:h:m:s]: 00:095:10:32:31
Block: 1348549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68037 RingCT/type: yes/0
Extra: 010f64d7fe9a78bf0f83fd0f2ec4d225949fbf20584290399d6876dea76e60e1d4021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac01aad208af8c110b7a425d2d13b6a25345bf948d04a6170911c45ae5dc862e 0.600000000000 1836476 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 dinasty-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": 1348559, "vin": [ { "gen": { "height": 1348549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac01aad208af8c110b7a425d2d13b6a25345bf948d04a6170911c45ae5dc862e" } } ], "extra": [ 1, 15, 100, 215, 254, 154, 120, 191, 15, 131, 253, 15, 46, 196, 210, 37, 148, 159, 191, 32, 88, 66, 144, 57, 157, 104, 118, 222, 167, 110, 96, 225, 212, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8