Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0580e1a76998f3d115c1fd2f69a87f00fb508f12f0cd9b8617a21cfb50fe76e0

Tx prefix hash: ffaecfb8cbdb6cae2171c6c3559d50f1c28105eacd20e040aede40ffa9b18b74
Tx public key: d316ae8f0bf26e62e92bf97965f47372a3dae42a3b9455ef77c249edd72d8dcf
Timestamp: 1762733629 Timestamp [UCT]: 2025-11-10 00:13:49 Age [y:d:h:m:s]: 00:016:14:24:12
Block: 1408717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11880 RingCT/type: yes/0
Extra: 01d316ae8f0bf26e62e92bf97965f47372a3dae42a3b9455ef77c249edd72d8dcf021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37c765b703402fde44b92fa50a7bad96b1ce53f19e700c58296fc46b90847540 0.600000000000 1897148 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": 1408727, "vin": [ { "gen": { "height": 1408717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37c765b703402fde44b92fa50a7bad96b1ce53f19e700c58296fc46b90847540" } } ], "extra": [ 1, 211, 22, 174, 143, 11, 242, 110, 98, 233, 43, 249, 121, 101, 244, 115, 114, 163, 218, 228, 42, 59, 148, 85, 239, 119, 194, 73, 237, 215, 45, 141, 207, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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