Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497a6cf7b74cdb0d8cc505c658f322a6c76541d319cc6985e4e2f4f8508f1884

Tx prefix hash: 050dc4cd6c720f57bd6d2357b32ed2ad934025f271cd0ea6259604f1bd9a6360
Tx public key: b9484b5338068133846d948058c3d06c381fd260a94b0f4081a5a2728ecfc8d3
Timestamp: 1761256187 Timestamp [UCT]: 2025-10-23 21:49:47 Age [y:d:h:m:s]: 00:071:16:54:49
Block: 1396484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51333 RingCT/type: yes/0
Extra: 01b9484b5338068133846d948058c3d06c381fd260a94b0f4081a5a2728ecfc8d3021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5450dec784eef9f242c06af8e17f325e210dcfbd8f6cf9248d1687ef12c0e7a1 0.600000000000 1884771 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": 1396494, "vin": [ { "gen": { "height": 1396484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5450dec784eef9f242c06af8e17f325e210dcfbd8f6cf9248d1687ef12c0e7a1" } } ], "extra": [ 1, 185, 72, 75, 83, 56, 6, 129, 51, 132, 109, 148, 128, 88, 195, 208, 108, 56, 31, 210, 96, 169, 75, 15, 64, 129, 165, 162, 114, 142, 207, 200, 211, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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