Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212df13830206d326eaecaf8094733117569768071ad4321fafcb845c6a0d056

Tx prefix hash: 22958d30e1b079f6b52cab1ea151704e6ec0ef15d3548dc9978db8bd8783f3c2
Tx public key: 6ecfd4434b08433df9427558df1a1688f7c9037089dde3fee3a3fe13afc43431
Timestamp: 1734360096 Timestamp [UCT]: 2024-12-16 14:41:36 Age [y:d:h:m:s]: 00:025:06:13:23
Block: 1176516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18045 RingCT/type: yes/0
Extra: 016ecfd4434b08433df9427558df1a1688f7c9037089dde3fee3a3fe13afc434310211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c61b937a1f80b0dd733833ac2bc5060e72d8b9a2d68f4156e674f6cf0d8645e0 0.600000000000 1662857 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": 1176526, "vin": [ { "gen": { "height": 1176516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c61b937a1f80b0dd733833ac2bc5060e72d8b9a2d68f4156e674f6cf0d8645e0" } } ], "extra": [ 1, 110, 207, 212, 67, 75, 8, 67, 61, 249, 66, 117, 88, 223, 26, 22, 136, 247, 201, 3, 112, 137, 221, 227, 254, 227, 163, 254, 19, 175, 196, 52, 49, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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