Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea7efe4453cfe09d3149f1e00d10b7615175e14e34f52e2b8525438b9cc9b9f6

Tx prefix hash: b004b0c2094f9552f90c1ae3d00668b40713cf9bb0a39e41354e67bdb2bd9bcc
Tx public key: 566b6ce451f9be88fdef7c5b91eadfcb8f9af8210b5c67a3eb95c0795ce84280
Timestamp: 1593656204 Timestamp [UCT]: 2020-07-02 02:16:44 Age [y:d:h:m:s]: 04:153:18:27:36
Block: 112578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1053370 RingCT/type: yes/0
Extra: 01566b6ce451f9be88fdef7c5b91eadfcb8f9af8210b5c67a3eb95c0795ce8428002110000000946a11e8a000000000000000000

1 output(s) for total of 260.005836486000 dcy

stealth address amount amount idx
00: b37c9a25e36bb2a6aaac013f007cacfe19e2127a43b0253885a184e49a7692a6 260.005836486000 194153 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": 112588, "vin": [ { "gen": { "height": 112578 } } ], "vout": [ { "amount": 260005836486, "target": { "key": "b37c9a25e36bb2a6aaac013f007cacfe19e2127a43b0253885a184e49a7692a6" } } ], "extra": [ 1, 86, 107, 108, 228, 81, 249, 190, 136, 253, 239, 124, 91, 145, 234, 223, 203, 143, 154, 248, 33, 11, 92, 103, 163, 235, 149, 192, 121, 92, 232, 66, 128, 2, 17, 0, 0, 0, 9, 70, 161, 30, 138, 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