Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae5d6ddb87312ec245545ce3b43fd4b1e86f014a98f99a0df178ea3ec96c62db

Tx prefix hash: 8e0ac85eab916105028415d8a7a1334ee72828bbece9930833021706686b767d
Tx public key: 95fed3a8547da406be5c924a5991faf64ff8f39aa02377c6d896699e9d50e320
Timestamp: 1710266947 Timestamp [UCT]: 2024-03-12 18:09:07 Age [y:d:h:m:s]: 01:023:09:30:30
Block: 976874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277695 RingCT/type: yes/0
Extra: 0195fed3a8547da406be5c924a5991faf64ff8f39aa02377c6d896699e9d50e3200211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7d717e4b8deb3b8fe1763fe42a4ce3a90b4bec1c8eeec02f27f8dda5e120970 0.600000000000 1436873 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": 976884, "vin": [ { "gen": { "height": 976874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7d717e4b8deb3b8fe1763fe42a4ce3a90b4bec1c8eeec02f27f8dda5e120970" } } ], "extra": [ 1, 149, 254, 211, 168, 84, 125, 164, 6, 190, 92, 146, 74, 89, 145, 250, 246, 79, 248, 243, 154, 160, 35, 119, 198, 216, 150, 105, 158, 157, 80, 227, 32, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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