Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf121dcd459a5761d7239719ce4986e180152a66b38573f91238b9bed0acc65

Tx prefix hash: aa6dc8966e0d7714f171670c189b7ba5b54ee7c2a8c56578272f82c8cd345c3b
Tx public key: 1e693edc22563f02a463702b5e88ccc90c0d834fd4df5ddf745e6396c4817525
Timestamp: 1696089921 Timestamp [UCT]: 2023-09-30 16:05:21 Age [y:d:h:m:s]: 01:201:02:38:47
Block: 859536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404792 RingCT/type: yes/0
Extra: 011e693edc22563f02a463702b5e88ccc90c0d834fd4df5ddf745e6396c481752502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.870964521000 dcy

stealth address amount amount idx
00: f66583d62bdf41265cb6ead645b7bd761370fc2a42c6c5bf29b5a9fd782b79d2 0.870964521000 1313766 of 0

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": 859546, "vin": [ { "gen": { "height": 859536 } } ], "vout": [ { "amount": 870964521, "target": { "key": "f66583d62bdf41265cb6ead645b7bd761370fc2a42c6c5bf29b5a9fd782b79d2" } } ], "extra": [ 1, 30, 105, 62, 220, 34, 86, 63, 2, 164, 99, 112, 43, 94, 136, 204, 201, 12, 13, 131, 79, 212, 223, 93, 223, 116, 94, 99, 150, 196, 129, 117, 37, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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