Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a54cd9e4db51185bd2e78598e8a2c7bb5ec8141e25c13621e78d1eea51e4c80b

Tx prefix hash: 883db6d8f658d74cb939b871b582fcebd82709c26beeb2390a7696b52deb86d7
Tx public key: 9ef98859b2457560517e69596ef06e01c5d41fbeb512b52f609d049fc78e0d7d
Timestamp: 1712719450 Timestamp [UCT]: 2024-04-10 03:24:10 Age [y:d:h:m:s]: 01:288:19:18:11
Block: 997177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465013 RingCT/type: yes/0
Extra: 019ef98859b2457560517e69596ef06e01c5d41fbeb512b52f609d049fc78e0d7d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16034e630e4694abc794f91f594f3f79ae6282cf4b7c835ae956bb7da1e9f83f 0.600000000000 1457607 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": 997187, "vin": [ { "gen": { "height": 997177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16034e630e4694abc794f91f594f3f79ae6282cf4b7c835ae956bb7da1e9f83f" } } ], "extra": [ 1, 158, 249, 136, 89, 178, 69, 117, 96, 81, 126, 105, 89, 110, 240, 110, 1, 197, 212, 31, 190, 181, 18, 181, 47, 96, 157, 4, 159, 199, 142, 13, 125, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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