Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb03d8dcba2e3db193115eb9f1a5cc7b72b451d2374eb7a8624f7f8124f0fd1c

Tx prefix hash: a1d328a5437dc1f4f2ac0dfeb1c9b7448beb12d81d7a2f7f58d43cae152e1d7d
Tx public key: e13b5b1c40ce15481a4e1401fc1d3d3eec5ec6e668ba071c775ba9d92843b021
Timestamp: 1711933360 Timestamp [UCT]: 2024-04-01 01:02:40 Age [y:d:h:m:s]: 01:044:09:11:46
Block: 990697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292693 RingCT/type: yes/0
Extra: 01e13b5b1c40ce15481a4e1401fc1d3d3eec5ec6e668ba071c775ba9d92843b0210211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb978d2bfe64b11da11a555561f8f084a705a7a4b9910087d556eb3042565ac 0.600000000000 1451023 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": 990707, "vin": [ { "gen": { "height": 990697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb978d2bfe64b11da11a555561f8f084a705a7a4b9910087d556eb3042565ac" } } ], "extra": [ 1, 225, 59, 91, 28, 64, 206, 21, 72, 26, 78, 20, 1, 252, 29, 61, 62, 236, 94, 198, 230, 104, 186, 7, 28, 119, 91, 169, 217, 40, 67, 176, 33, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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