Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee440d0f05b5cbfd93e11388fbbf6b333733f6478c1a10c251155e376916537

Tx prefix hash: 9cd40badcbe2e9be9503338578385d3d7c16d473ea9060a527ca085967285909
Tx public key: 2ea4ebdac7cc6c6dbab2ad0e470321769aff316fa33ffeb0d7a6fb834703d288
Timestamp: 1699515728 Timestamp [UCT]: 2023-11-09 07:42:08 Age [y:d:h:m:s]: 01:090:00:05:33
Block: 887740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325474 RingCT/type: yes/0
Extra: 012ea4ebdac7cc6c6dbab2ad0e470321769aff316fa33ffeb0d7a6fb834703d288021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.702342361000 dcy

stealth address amount amount idx
00: 002175540665ea0ee13d97ce3ae3abb1a6a50b4828a359a7b43749d43b77765e 0.702342361000 1343635 of 0

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": 887750, "vin": [ { "gen": { "height": 887740 } } ], "vout": [ { "amount": 702342361, "target": { "key": "002175540665ea0ee13d97ce3ae3abb1a6a50b4828a359a7b43749d43b77765e" } } ], "extra": [ 1, 46, 164, 235, 218, 199, 204, 108, 109, 186, 178, 173, 14, 71, 3, 33, 118, 154, 255, 49, 111, 163, 63, 254, 176, 215, 166, 251, 131, 71, 3, 210, 136, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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