Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e4befeb11fcc24b8d608c65af3f6844532f26af8e2b32fbbc793fbc9679fd8f

Tx prefix hash: e6f36470a9b69f47e33104a1f2c0a880c3214651673e33b4b9951350972bfb3a
Tx public key: c0867a2bf86cc79cad02a868a0d569f45e4dfcce460428f496b24e364f6cbbe9
Timestamp: 1743434813 Timestamp [UCT]: 2025-03-31 15:26:53 Age [y:d:h:m:s]: 00:222:11:22:50
Block: 1251349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156723 RingCT/type: yes/0
Extra: 01c0867a2bf86cc79cad02a868a0d569f45e4dfcce460428f496b24e364f6cbbe9021100000001def6842b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250bb2defc828f3b5f0f6976ed46a21f95fc3dfd0aac3a0172e2df9541b2e63d 0.600000000000 1738412 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": 1251359, "vin": [ { "gen": { "height": 1251349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250bb2defc828f3b5f0f6976ed46a21f95fc3dfd0aac3a0172e2df9541b2e63d" } } ], "extra": [ 1, 192, 134, 122, 43, 248, 108, 199, 156, 173, 2, 168, 104, 160, 213, 105, 244, 94, 77, 252, 206, 70, 4, 40, 244, 150, 178, 78, 54, 79, 108, 187, 233, 2, 17, 0, 0, 0, 1, 222, 246, 132, 43, 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