Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce97e59dbb27cc8ab09533320c2ac9b6e68015f78630e5369f289b0109112b5

Tx prefix hash: 85b764986c9cd3864dc9d42da07ae06e14e2ea0b9f6eab09d8bd874cd39051e6
Tx public key: 9b40a981f8dbfcbf468ae5d23626b30adf4e86c4b713fb375e4a848e3af4fe1e
Timestamp: 1699061435 Timestamp [UCT]: 2023-11-04 01:30:35 Age [y:d:h:m:s]: 01:215:02:55:42
Block: 884173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414778 RingCT/type: yes/0
Extra: 019b40a981f8dbfcbf468ae5d23626b30adf4e86c4b713fb375e4a848e3af4fe1e021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.721718470000 dcy

stealth address amount amount idx
00: c96af31db225519f53a367cf5ee0838c28c4b265df7f332b370074713e7b3a20 0.721718470000 1339906 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": 884183, "vin": [ { "gen": { "height": 884173 } } ], "vout": [ { "amount": 721718470, "target": { "key": "c96af31db225519f53a367cf5ee0838c28c4b265df7f332b370074713e7b3a20" } } ], "extra": [ 1, 155, 64, 169, 129, 248, 219, 252, 191, 70, 138, 229, 210, 54, 38, 179, 10, 223, 78, 134, 196, 183, 19, 251, 55, 94, 74, 132, 142, 58, 244, 254, 30, 2, 17, 0, 0, 0, 1, 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