Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1221cff95adfd07a9754d3b58f7b66be2ae4e2bade4e69b699d0c3f0cc3b7b66

Tx prefix hash: 62ade0ab930778779ce378cb4fc3af6d6c0fc407a63b00428c7fa9bda8900569
Tx public key: 6e8940a8d69716bf345b4edec01ec36740c49ee23c8a1f0027880a4cf88384ac
Timestamp: 1720677678 Timestamp [UCT]: 2024-07-11 06:01:18 Age [y:d:h:m:s]: 01:125:00:23:48
Block: 1063184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347862 RingCT/type: yes/0
Extra: 016e8940a8d69716bf345b4edec01ec36740c49ee23c8a1f0027880a4cf88384ac02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72dc2013a4a3fbc9cd7d2ea654b390782a01e4afff662fa4b1c352d60ff6a1ab 0.600000000000 1533699 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": 1063194, "vin": [ { "gen": { "height": 1063184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72dc2013a4a3fbc9cd7d2ea654b390782a01e4afff662fa4b1c352d60ff6a1ab" } } ], "extra": [ 1, 110, 137, 64, 168, 214, 151, 22, 191, 52, 91, 78, 222, 192, 30, 195, 103, 64, 196, 158, 226, 60, 138, 31, 0, 39, 136, 10, 76, 248, 131, 132, 172, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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