Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e99fa9fdc263da09111361cab3030423ddeb6fd3609c76fadba3d5092f395831

Tx prefix hash: 92d5277a71022e77b4a2635fb0af9e90c3cb0176fcc2917f76c0c8401a6b6805
Tx public key: 7f80a629c8867edf3a9ca5c84518e60f803703b991c92179571ec9f8e5fe630b
Timestamp: 1707467607 Timestamp [UCT]: 2024-02-09 08:33:27 Age [y:d:h:m:s]: 01:067:20:57:01
Block: 953650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309556 RingCT/type: yes/0
Extra: 017f80a629c8867edf3a9ca5c84518e60f803703b991c92179571ec9f8e5fe630b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35eff0c468eeba576981994b19ede82222cc4158eb6a1c8b532b5c4d444d1fbf 0.600000000000 1412886 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": 953660, "vin": [ { "gen": { "height": 953650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35eff0c468eeba576981994b19ede82222cc4158eb6a1c8b532b5c4d444d1fbf" } } ], "extra": [ 1, 127, 128, 166, 41, 200, 134, 126, 223, 58, 156, 165, 200, 69, 24, 230, 15, 128, 55, 3, 185, 145, 201, 33, 121, 87, 30, 201, 248, 229, 254, 99, 11, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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