Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d86442a801428fb920a682d769593e2646c2a3f18adc6fcc3e3e8c566f752616

Tx prefix hash: 7f92a9c74a872aa67f9f7a6083e29f24758a31811b27d0979e3656b65fb7751e
Tx public key: 7bf00a85db252ead2a30b3a484e73b2b0bc31a0b682009aafee22859a1c199b3
Timestamp: 1581539394 Timestamp [UCT]: 2020-02-12 20:29:54 Age [y:d:h:m:s]: 04:327:16:55:56
Block: 63724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126329 RingCT/type: yes/0
Extra: 017bf00a85db252ead2a30b3a484e73b2b0bc31a0b682009aafee22859a1c199b30211000000054ac5aa02000000000000000000

1 output(s) for total of 377.447669119000 dcy

stealth address amount amount idx
00: a01837565b12e60c7a5a2866cc9ed174b247c9ff83ea095f0286952158b4f403 377.447669119000 117445 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": 63734, "vin": [ { "gen": { "height": 63724 } } ], "vout": [ { "amount": 377447669119, "target": { "key": "a01837565b12e60c7a5a2866cc9ed174b247c9ff83ea095f0286952158b4f403" } } ], "extra": [ 1, 123, 240, 10, 133, 219, 37, 46, 173, 42, 48, 179, 164, 132, 231, 59, 43, 11, 195, 26, 11, 104, 32, 9, 170, 254, 226, 40, 89, 161, 193, 153, 179, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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