Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87259191f5c0474d5dda6f230f04101bed0ad0475893f927049fd908a2f1ed08

Tx prefix hash: 6d4c04d8050d5b9ed54741e582be34337d2ff74297f8cef59ee7846bb40bc55f
Tx public key: 05d50df411014a0b20e835d09fef6060a94bf34a34884f799a314f1e8c3ecab8
Timestamp: 1659157778 Timestamp [UCT]: 2022-07-30 05:09:38 Age [y:d:h:m:s]: 02:110:06:44:09
Block: 554743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600211 RingCT/type: yes/0
Extra: 0105d50df411014a0b20e835d09fef6060a94bf34a34884f799a314f1e8c3ecab802110000000175e3f0e9000000000000000000

1 output(s) for total of 8.910586316000 dcy

stealth address amount amount idx
00: 7716bd937acdd574ca7d728f617d503f8897619c31039c781a09843cba5a65d0 8.910586316000 986605 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": 554753, "vin": [ { "gen": { "height": 554743 } } ], "vout": [ { "amount": 8910586316, "target": { "key": "7716bd937acdd574ca7d728f617d503f8897619c31039c781a09843cba5a65d0" } } ], "extra": [ 1, 5, 213, 13, 244, 17, 1, 74, 11, 32, 232, 53, 208, 159, 239, 96, 96, 169, 75, 243, 74, 52, 136, 79, 121, 154, 49, 79, 30, 140, 62, 202, 184, 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