Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f76951a9393b4ca1b75e9c54c5bcf5c1d3935540b9fa350f213def67769eb67b

Tx prefix hash: 96000d8de9abe8b28d3a55538f463ebc919b7ad184656e1dbdf58cd5d330ca9f
Tx public key: d5dd2c4ce0be34557ed06e9d4f36b45daaeb4d11d97daae2e0912402bdc26c00
Timestamp: 1750533017 Timestamp [UCT]: 2025-06-21 19:10:17 Age [y:d:h:m:s]: 00:152:08:51:25
Block: 1309950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106740 RingCT/type: yes/0
Extra: 01d5dd2c4ce0be34557ed06e9d4f36b45daaeb4d11d97daae2e0912402bdc26c00021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aa3d83505c1ffbf0baefd7da83daf5921280b109763827d87145e17e8913648 0.600000000000 1797567 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": 1309960, "vin": [ { "gen": { "height": 1309950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aa3d83505c1ffbf0baefd7da83daf5921280b109763827d87145e17e8913648" } } ], "extra": [ 1, 213, 221, 44, 76, 224, 190, 52, 85, 126, 208, 110, 157, 79, 54, 180, 93, 170, 235, 77, 17, 217, 125, 170, 226, 224, 145, 36, 2, 189, 194, 108, 0, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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