Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a4ad135b7695cba13acec82edc3d4a58189b364a91983c19458390704e5e7d

Tx prefix hash: f81c6a84fd4856cfcaacb25e0fdf618bc2636608a355bbc827b579436f6b4619
Tx public key: 8d5cde262f950f067d31ea975e588e7858dd00c0de4656931e8da9cbfa99e2b8
Timestamp: 1705677514 Timestamp [UCT]: 2024-01-19 15:18:34 Age [y:d:h:m:s]: 01:079:12:20:22
Block: 938785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317922 RingCT/type: yes/0
Extra: 018d5cde262f950f067d31ea975e588e7858dd00c0de4656931e8da9cbfa99e2b802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b727cf16d30577be4d008353edbc6a63909606abc6ca6903bf58d9a06b282e7 0.600000000000 1396863 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": 938795, "vin": [ { "gen": { "height": 938785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b727cf16d30577be4d008353edbc6a63909606abc6ca6903bf58d9a06b282e7" } } ], "extra": [ 1, 141, 92, 222, 38, 47, 149, 15, 6, 125, 49, 234, 151, 94, 88, 142, 120, 88, 221, 0, 192, 222, 70, 86, 147, 30, 141, 169, 203, 250, 153, 226, 184, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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