Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3def57403d778617e60f93fd7751c80bebb3d3afd3b3f10e8e9188f5f9bca389

Tx prefix hash: 016c46ca0344c4961d32adf4e9faa31f956f809076cf9d1f274c847e3af990c7
Tx public key: 41e5db940b2d7b49eb1103a4f147b8e49ee9e870bc0cdbc1af4ac3b85dc894e5
Timestamp: 1762191342 Timestamp [UCT]: 2025-11-03 17:35:42 Age [y:d:h:m:s]: 00:016:14:25:47
Block: 1404215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11892 RingCT/type: yes/0
Extra: 0141e5db940b2d7b49eb1103a4f147b8e49ee9e870bc0cdbc1af4ac3b85dc894e502110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59c1105712061140638d97d74c704a387e9c1eeaf25bef669a3bcd645ec23611 0.600000000000 1892572 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": 1404225, "vin": [ { "gen": { "height": 1404215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59c1105712061140638d97d74c704a387e9c1eeaf25bef669a3bcd645ec23611" } } ], "extra": [ 1, 65, 229, 219, 148, 11, 45, 123, 73, 235, 17, 3, 164, 241, 71, 184, 228, 158, 233, 232, 112, 188, 12, 219, 193, 175, 74, 195, 184, 93, 200, 148, 229, 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