Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6201e8e58d6529d313e9c4d3922348b0c38237eea75cd240af1de0bc8bfd1fb

Tx prefix hash: cf828828f724fee4e71fc8d30929b16fd296f9441a95564f1377b15f1f2b37c9
Tx public key: a453f0040fa3fc37ad553899adb9c0ee9f89f3ba77c16f2f069550f428ebda1b
Timestamp: 1711300768 Timestamp [UCT]: 2024-03-24 17:19:28 Age [y:d:h:m:s]: 01:005:19:09:43
Block: 985455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265085 RingCT/type: yes/0
Extra: 01a453f0040fa3fc37ad553899adb9c0ee9f89f3ba77c16f2f069550f428ebda1b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbdce329a11a9df3038b2525f936e91c2d1e2942b2741e439a401314f805f96f 0.600000000000 1445666 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": 985465, "vin": [ { "gen": { "height": 985455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbdce329a11a9df3038b2525f936e91c2d1e2942b2741e439a401314f805f96f" } } ], "extra": [ 1, 164, 83, 240, 4, 15, 163, 252, 55, 173, 85, 56, 153, 173, 185, 192, 238, 159, 137, 243, 186, 119, 193, 111, 47, 6, 149, 80, 244, 40, 235, 218, 27, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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