Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ef480a8de2a59614fffbe7c53d70bdcb602bb9770d815e6496e4eb0ada7af4

Tx prefix hash: c807582590ec765ebf286167817fef33b921980519d3afdc19e3a792c92d26df
Tx public key: 29a3b37e17bc5340dfa748dbbd771dc1ec6a64e7e206e3f9f3a409d0c80ce725
Timestamp: 1759613252 Timestamp [UCT]: 2025-10-04 21:27:32 Age [y:d:h:m:s]: 00:003:22:17:08
Block: 1382848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2811 RingCT/type: yes/0
Extra: 0129a3b37e17bc5340dfa748dbbd771dc1ec6a64e7e206e3f9f3a409d0c80ce725021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3bc3cfd1a57184a40ad831fa8e613dbb76c45abcd0ff11a83d61127e72f5adb 0.600000000000 1870991 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": 1382858, "vin": [ { "gen": { "height": 1382848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3bc3cfd1a57184a40ad831fa8e613dbb76c45abcd0ff11a83d61127e72f5adb" } } ], "extra": [ 1, 41, 163, 179, 126, 23, 188, 83, 64, 223, 167, 72, 219, 189, 119, 29, 193, 236, 106, 100, 231, 226, 6, 227, 249, 243, 164, 9, 208, 200, 12, 231, 37, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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