Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9079b355467921fe0fd1e40d0429df1201451bc431b33a198494114c0a400fcb

Tx prefix hash: 29a7826ca24542bd44088538c82d7f8145a9b75cfd60abb15b9410ab36c37b87
Tx public key: 7e8791ed49f258491ce568c213f7f0b26f3b926e6e963d323b58e93b54ae4546
Timestamp: 1580813122 Timestamp [UCT]: 2020-02-04 10:45:22 Age [y:d:h:m:s]: 04:323:15:51:14
Block: 58607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122571 RingCT/type: yes/0
Extra: 017e8791ed49f258491ce568c213f7f0b26f3b926e6e963d323b58e93b54ae454602110000000a4ac5aa02000000000000000000

1 output(s) for total of 392.474550241000 dcy

stealth address amount amount idx
00: 0946ccc496a4091a4e9530d12d2d74b3061ef1ff7530d8170aa63ca072c66746 392.474550241000 108263 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": 58617, "vin": [ { "gen": { "height": 58607 } } ], "vout": [ { "amount": 392474550241, "target": { "key": "0946ccc496a4091a4e9530d12d2d74b3061ef1ff7530d8170aa63ca072c66746" } } ], "extra": [ 1, 126, 135, 145, 237, 73, 242, 88, 73, 28, 229, 104, 194, 19, 247, 240, 178, 111, 59, 146, 110, 110, 150, 61, 50, 59, 88, 233, 59, 84, 174, 69, 70, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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