Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b57a035b6a0bb328a6877038f61efce7c0698904c7b28fce671921fa22a4002

Tx prefix hash: ca13e68db0ef3c8d84a2432863977600bc1baea2b169e1e867966759ae9df88e
Tx public key: 6e20a6d29cc084d90c8688aec77db157fbdbcd16f0e541b64602924b952ed7d4
Timestamp: 1723363168 Timestamp [UCT]: 2024-08-11 07:59:28 Age [y:d:h:m:s]: 00:303:13:32:23
Block: 1085445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216881 RingCT/type: yes/0
Extra: 016e20a6d29cc084d90c8688aec77db157fbdbcd16f0e541b64602924b952ed7d4021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e20499f7f0685ebe7296d4a2eccf9d0fece75ce943a66312609eb8a0faccac66 0.600000000000 1560028 of 15

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": 1085455, "vin": [ { "gen": { "height": 1085445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20499f7f0685ebe7296d4a2eccf9d0fece75ce943a66312609eb8a0faccac66" } } ], "extra": [ 1, 110, 32, 166, 210, 156, 192, 132, 217, 12, 134, 136, 174, 199, 125, 177, 87, 251, 219, 205, 22, 240, 229, 65, 182, 70, 2, 146, 75, 149, 46, 215, 212, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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