Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccaa84889814b493e37365426b4e51108fca00826abc76bd78257cc801719ea9

Tx prefix hash: 995d88ce1087163fc3ee674216e43c7e862c100c658d957070e0088b5a133cda
Tx public key: 238c8bc1b69b8fb4832e2b9ebf6ab55f438beb86be1ecb9aab3a955c7e84352c
Timestamp: 1580897237 Timestamp [UCT]: 2020-02-05 10:07:17 Age [y:d:h:m:s]: 04:296:16:17:22
Block: 59242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103288 RingCT/type: yes/0
Extra: 01238c8bc1b69b8fb4832e2b9ebf6ab55f438beb86be1ecb9aab3a955c7e84352c0211000000d517786bcf000000000000000000

1 output(s) for total of 390.584493513000 dcy

stealth address amount amount idx
00: 05fd7edf5791ae51fbddecff1b1aeac9c96b0522bb57b360484b35df924bebd4 390.584493513000 109356 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": 59252, "vin": [ { "gen": { "height": 59242 } } ], "vout": [ { "amount": 390584493513, "target": { "key": "05fd7edf5791ae51fbddecff1b1aeac9c96b0522bb57b360484b35df924bebd4" } } ], "extra": [ 1, 35, 140, 139, 193, 182, 155, 143, 180, 131, 46, 43, 158, 191, 106, 181, 95, 67, 139, 235, 134, 190, 30, 203, 154, 171, 58, 149, 92, 126, 132, 53, 44, 2, 17, 0, 0, 0, 213, 23, 120, 107, 207, 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