Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea703a56d9083b42b9f3c871a4babe589cd73435016f68b836070b73e781c81

Tx prefix hash: 976b0db1c3c43548ea21fba306d3dbd35adb9f6abd101562d579e8c36ce8146f
Tx public key: 80a5c6bcaa3e5033fef1582e7370043cf8cd01955fed997888def13e53048ed1
Timestamp: 1722062293 Timestamp [UCT]: 2024-07-27 06:38:13 Age [y:d:h:m:s]: 00:249:09:02:26
Block: 1074650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178143 RingCT/type: yes/0
Extra: 0180a5c6bcaa3e5033fef1582e7370043cf8cd01955fed997888def13e53048ed1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f47e8c322d1014f1f496b7fdc6fbb2d241f71bca2af0c4214e6b52d6b4c938b 0.600000000000 1547167 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": 1074660, "vin": [ { "gen": { "height": 1074650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f47e8c322d1014f1f496b7fdc6fbb2d241f71bca2af0c4214e6b52d6b4c938b" } } ], "extra": [ 1, 128, 165, 198, 188, 170, 62, 80, 51, 254, 241, 88, 46, 115, 112, 4, 60, 248, 205, 1, 149, 95, 237, 153, 120, 136, 222, 241, 62, 83, 4, 142, 209, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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