Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5622ddc1c80845bdbd84762079d5f096dc8c7074b919240ca580a0031871b697

Tx prefix hash: e8c286aca53a9950df69fd505d829e2d9afbcc76a8bd09fd695b6743ff2573a3
Tx public key: cfbe69f77affb28cd8ae8902c3ef26e1724558ab915c18c11926b14f0b11d6c8
Timestamp: 1583751910 Timestamp [UCT]: 2020-03-09 11:05:10 Age [y:d:h:m:s]: 04:251:14:53:09
Block: 79227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074695 RingCT/type: yes/0
Extra: 01cfbe69f77affb28cd8ae8902c3ef26e1724558ab915c18c11926b14f0b11d6c802110000000c6d997e00000000000000000000

1 output(s) for total of 335.342695882000 dcy

stealth address amount amount idx
00: 1a3bfd3682a14e43fddedca5044aca154a27fec9bfd683b7ce426f204a79f8d4 335.342695882000 145003 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": 79237, "vin": [ { "gen": { "height": 79227 } } ], "vout": [ { "amount": 335342695882, "target": { "key": "1a3bfd3682a14e43fddedca5044aca154a27fec9bfd683b7ce426f204a79f8d4" } } ], "extra": [ 1, 207, 190, 105, 247, 122, 255, 178, 140, 216, 174, 137, 2, 195, 239, 38, 225, 114, 69, 88, 171, 145, 92, 24, 193, 25, 38, 177, 79, 11, 17, 214, 200, 2, 17, 0, 0, 0, 12, 109, 153, 126, 0, 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