Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1ab975f30ab6a34b2e309f1a7451e80556d0d8c5141be91173bb1de3beceab

Tx prefix hash: 35c3f2ac0ffc47ff720d8a42fd5060fe5745833e2f3804d65ad2446d52df6591
Tx public key: 697aabf80186b0ec5052131120c5e6ef45a9b45cba1ee71f9184eefe0df0e6d0
Timestamp: 1736452554 Timestamp [UCT]: 2025-01-09 19:55:54 Age [y:d:h:m:s]: 00:162:10:45:44
Block: 1193815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115759 RingCT/type: yes/0
Extra: 01697aabf80186b0ec5052131120c5e6ef45a9b45cba1ee71f9184eefe0df0e6d00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3958ee522ebbb75c2490f220734baa935bb74c9c6a1def6acb05c79abc74566f 0.600000000000 1680380 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": 1193825, "vin": [ { "gen": { "height": 1193815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3958ee522ebbb75c2490f220734baa935bb74c9c6a1def6acb05c79abc74566f" } } ], "extra": [ 1, 105, 122, 171, 248, 1, 134, 176, 236, 80, 82, 19, 17, 32, 197, 230, 239, 69, 169, 180, 92, 186, 30, 231, 31, 145, 132, 238, 254, 13, 240, 230, 208, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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