Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e6a87075ea35815087d695cdb409306c6029ced63e49ac70d1cc125f1d488a7

Tx prefix hash: 416e3e54f8176d184bf8a848204a45545a27bef29d47d4afc8ea77d195196ae0
Tx public key: 18efc9bb72efdb7da45fb7e50f930361adea5ec354d2b7d4c4a20dbefca91647
Timestamp: 1686030835 Timestamp [UCT]: 2023-06-06 05:53:55 Age [y:d:h:m:s]: 02:016:09:49:16
Block: 776170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533681 RingCT/type: yes/0
Extra: 0118efc9bb72efdb7da45fb7e50f930361adea5ec354d2b7d4c4a20dbefca9164702110000000233af99f4000000000000000000

1 output(s) for total of 1.645230497000 dcy

stealth address amount amount idx
00: f5bacb8316e72a84a7735301e07ca28425c00a6a7816ffc0b65c0a0b2fe9944e 1.645230497000 1225707 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": 776180, "vin": [ { "gen": { "height": 776170 } } ], "vout": [ { "amount": 1645230497, "target": { "key": "f5bacb8316e72a84a7735301e07ca28425c00a6a7816ffc0b65c0a0b2fe9944e" } } ], "extra": [ 1, 24, 239, 201, 187, 114, 239, 219, 125, 164, 95, 183, 229, 15, 147, 3, 97, 173, 234, 94, 195, 84, 210, 183, 212, 196, 162, 13, 190, 252, 169, 22, 71, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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