Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db59a811c4e70b1caac5182c13539b38259891e335e8cf9c9979f3dce1bed7fe

Tx prefix hash: 0161a24479e1085bdecfda372349fb71db114c5eecfc1a7e8835cbd7abdb19a1
Tx public key: d5b15842eb39f328f5b90c4d23cee90f1e19d1c801b669936b33f776b2d8bb89
Timestamp: 1763541740 Timestamp [UCT]: 2025-11-19 08:42:20 Age [y:d:h:m:s]: 00:008:21:08:55
Block: 1415402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6366 RingCT/type: yes/0
Extra: 01d5b15842eb39f328f5b90c4d23cee90f1e19d1c801b669936b33f776b2d8bb890211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a470b6e93683129267d052e181dd774245a3faaf8794be8a40944afadd8c5b4 0.600000000000 1903903 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": 1415412, "vin": [ { "gen": { "height": 1415402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a470b6e93683129267d052e181dd774245a3faaf8794be8a40944afadd8c5b4" } } ], "extra": [ 1, 213, 177, 88, 66, 235, 57, 243, 40, 245, 185, 12, 77, 35, 206, 233, 15, 30, 25, 209, 200, 1, 182, 105, 147, 107, 51, 247, 118, 178, 216, 187, 137, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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