Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6eeda45491c729d3d962e0703f631a9fe1fb3803ca04e2c1c35c8f6d89fbe76

Tx prefix hash: 76488d163cfb20b6ef956f242f81bca4d383b21ffd7be515717fcbadd02fb4f2
Tx public key: 70601dfaca750da4d88400c9e05fc9c0e909fe45c6db0369e047193c6dcf8f9f
Timestamp: 1742100325 Timestamp [UCT]: 2025-03-16 04:45:25 Age [y:d:h:m:s]: 00:290:08:27:57
Block: 1240317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205298 RingCT/type: yes/0
Extra: 0170601dfaca750da4d88400c9e05fc9c0e909fe45c6db0369e047193c6dcf8f9f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a23a8f6bb78f324eb50d109d897553eeb2892addd47f40975b4fab756e47427c 0.600000000000 1727282 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": 1240327, "vin": [ { "gen": { "height": 1240317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23a8f6bb78f324eb50d109d897553eeb2892addd47f40975b4fab756e47427c" } } ], "extra": [ 1, 112, 96, 29, 250, 202, 117, 13, 164, 216, 132, 0, 201, 224, 95, 201, 192, 233, 9, 254, 69, 198, 219, 3, 105, 224, 71, 25, 60, 109, 207, 143, 159, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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