Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206b1f0b2317d958c82c677db64fee0f5443f503ec7e7d09694d9124edfbbe6e

Tx prefix hash: 7b66e4104d759e892d291c30e179caac2d192deab51f851cdd6a113aa6a988ac
Tx public key: 48384725b4a652f496c657ace81c878609d5e2d276e1af9fab7f80ea2de2d900
Timestamp: 1705081927 Timestamp [UCT]: 2024-01-12 17:52:07 Age [y:d:h:m:s]: 01:074:07:28:20
Block: 933858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314193 RingCT/type: yes/0
Extra: 0148384725b4a652f496c657ace81c878609d5e2d276e1af9fab7f80ea2de2d9000211000000130011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 441b62c506c9e5271ee1555e6605f520acefd6cf125a8097197a3e20300c8a1c 0.600000000000 1391842 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": 933868, "vin": [ { "gen": { "height": 933858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "441b62c506c9e5271ee1555e6605f520acefd6cf125a8097197a3e20300c8a1c" } } ], "extra": [ 1, 72, 56, 71, 37, 180, 166, 82, 244, 150, 198, 87, 172, 232, 28, 135, 134, 9, 213, 226, 210, 118, 225, 175, 159, 171, 127, 128, 234, 45, 226, 217, 0, 2, 17, 0, 0, 0, 19, 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