Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e201a667a7a54f9f115bc5ad2dbb2f44cfb382421a7a698d1ba4abf6ad0d4326

Tx prefix hash: bb4644fc612c18de683dd5f04254b013954bd7b968d6bef391c61bcf17eb3e01
Tx public key: de877f3bac5d0b9df7a1f73924adfa5d23f7076c4f1716255debe3caec50dd65
Timestamp: 1698492968 Timestamp [UCT]: 2023-10-28 11:36:08 Age [y:d:h:m:s]: 01:155:21:37:39
Block: 879485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372388 RingCT/type: yes/0
Extra: 01de877f3bac5d0b9df7a1f73924adfa5d23f7076c4f1716255debe3caec50dd650211000000064b8f5122000000000000000000

1 output(s) for total of 0.747999172000 dcy

stealth address amount amount idx
00: 1a0b2d1eac59028473c691f0df01d2d01eb236576c570f3e483dae0543537105 0.747999172000 1335009 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": 879495, "vin": [ { "gen": { "height": 879485 } } ], "vout": [ { "amount": 747999172, "target": { "key": "1a0b2d1eac59028473c691f0df01d2d01eb236576c570f3e483dae0543537105" } } ], "extra": [ 1, 222, 135, 127, 59, 172, 93, 11, 157, 247, 161, 247, 57, 36, 173, 250, 93, 35, 247, 7, 108, 79, 23, 22, 37, 93, 235, 227, 202, 236, 80, 221, 101, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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