Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef74331fc0e057c294bd94ac6ae0fc9d500379e02e1a35fd8585cbd97270a50

Tx prefix hash: b54eb6e212ddbc4a9ef1d7eb8872497672bb20a899dfc4b5381619872b8edc4c
Tx public key: 94d9b15be3501b607e0c4a7c4b80048762e653a9efa75c3aa9cac11ab3adb331
Timestamp: 1761065690 Timestamp [UCT]: 2025-10-21 16:54:50 Age [y:d:h:m:s]: 00:063:07:22:31
Block: 1394899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45316 RingCT/type: yes/0
Extra: 0194d9b15be3501b607e0c4a7c4b80048762e653a9efa75c3aa9cac11ab3adb33102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 740a3f038b74cddb0232911b1056ea0962fb956ed0e234ef5c953a4975f0f272 0.600000000000 1883174 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": 1394909, "vin": [ { "gen": { "height": 1394899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740a3f038b74cddb0232911b1056ea0962fb956ed0e234ef5c953a4975f0f272" } } ], "extra": [ 1, 148, 217, 177, 91, 227, 80, 27, 96, 126, 12, 74, 124, 75, 128, 4, 135, 98, 230, 83, 169, 239, 167, 92, 58, 169, 202, 193, 26, 179, 173, 179, 49, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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