Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32ab86a69fc5a5d5c0d3d01d3e1c5501ff05aa6437f32ba9e8a379ed266347b1

Tx prefix hash: e0a67cea0eae622cc8a6c0da9a901d0dc51a7c347f6a7a1aebaed9de5c82daea
Tx public key: 9c90fd4a97d33e7d539666689d3d5f92f4cca4c50bbf43b2c5505d53fab1ed11
Timestamp: 1711655092 Timestamp [UCT]: 2024-03-28 19:44:52 Age [y:d:h:m:s]: 00:357:02:13:04
Block: 988390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255305 RingCT/type: yes/0
Extra: 019c90fd4a97d33e7d539666689d3d5f92f4cca4c50bbf43b2c5505d53fab1ed1102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4733985fb3e13be17bdbe0f0d73e80abc071d37d6e28827ff83a7a324e349b33 0.600000000000 1448669 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": 988400, "vin": [ { "gen": { "height": 988390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4733985fb3e13be17bdbe0f0d73e80abc071d37d6e28827ff83a7a324e349b33" } } ], "extra": [ 1, 156, 144, 253, 74, 151, 211, 62, 125, 83, 150, 102, 104, 157, 61, 95, 146, 244, 204, 164, 197, 11, 191, 67, 178, 197, 80, 93, 83, 250, 177, 237, 17, 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