Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56314000d02e7c53a9e782805672a4e83b838302b154894137b8da8fc234261

Tx prefix hash: 479fd49d8d5d7c00a87b331d50c674e91967bc51af5e3b72045eae9c340231cb
Tx public key: 5e4067b383857afbe2ae639e4bfd558889bc0ebd7ec03f5c6f58905dcb8bc98a
Timestamp: 1723714699 Timestamp [UCT]: 2024-08-15 09:38:19 Age [y:d:h:m:s]: 00:214:02:58:22
Block: 1088359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152913 RingCT/type: yes/0
Extra: 015e4067b383857afbe2ae639e4bfd558889bc0ebd7ec03f5c6f58905dcb8bc98a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8822ae8c3befb90f684c2d3cdc870821ee70ac531ccbc3707345c9296141dd49 0.600000000000 1562974 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": 1088369, "vin": [ { "gen": { "height": 1088359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8822ae8c3befb90f684c2d3cdc870821ee70ac531ccbc3707345c9296141dd49" } } ], "extra": [ 1, 94, 64, 103, 179, 131, 133, 122, 251, 226, 174, 99, 158, 75, 253, 85, 136, 137, 188, 14, 189, 126, 192, 63, 92, 111, 88, 144, 93, 203, 139, 201, 138, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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