Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e50f06d7377729837f19ec15668b1f75f9a5b7856f5cb08a9be349dd473be5b5

Tx prefix hash: a62437f0eab38d14f7ac5695159904aa6376051de54bd8c7b36ba5b8288c330c
Tx public key: cb56b268f343dd5ed933938bd40c9be097b4dfbbd2a03d3dfd67dcca0c7a15d4
Timestamp: 1697425955 Timestamp [UCT]: 2023-10-16 03:12:35 Age [y:d:h:m:s]: 01:168:11:30:36
Block: 870604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381435 RingCT/type: yes/0
Extra: 01cb56b268f343dd5ed933938bd40c9be097b4dfbbd2a03d3dfd67dcca0c7a15d40211000000024b8f5122000000000000000000

1 output(s) for total of 0.800437763000 dcy

stealth address amount amount idx
00: f27e50001134fb196a34cb269921b2097d504099e6d0139139df5e565248c054 0.800437763000 1325487 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": 870614, "vin": [ { "gen": { "height": 870604 } } ], "vout": [ { "amount": 800437763, "target": { "key": "f27e50001134fb196a34cb269921b2097d504099e6d0139139df5e565248c054" } } ], "extra": [ 1, 203, 86, 178, 104, 243, 67, 221, 94, 217, 51, 147, 139, 212, 12, 155, 224, 151, 180, 223, 187, 210, 160, 61, 61, 253, 103, 220, 202, 12, 122, 21, 212, 2, 17, 0, 0, 0, 2, 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