Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ad2cccfd4ca6fab89ed06ce3599adf32b6a0ab0c34f0fc473efc401cb672c6

Tx prefix hash: 1e0a693a6b4f75ec335a14829ad977887993a99b6a4cc4f8522599b09aa7b5e0
Tx public key: c80d8c7539ce8ddc8641408f7eca9f7375a9ead85e727de9e41c9584db77eb77
Timestamp: 1712164697 Timestamp [UCT]: 2024-04-03 17:18:17 Age [y:d:h:m:s]: 00:356:12:00:06
Block: 992578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254880 RingCT/type: yes/0
Extra: 01c80d8c7539ce8ddc8641408f7eca9f7375a9ead85e727de9e41c9584db77eb7702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe399a5cd549e5512592cf68fb802de4e5be256fed56ea332a541381eba68f5 0.600000000000 1452934 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": 992588, "vin": [ { "gen": { "height": 992578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe399a5cd549e5512592cf68fb802de4e5be256fed56ea332a541381eba68f5" } } ], "extra": [ 1, 200, 13, 140, 117, 57, 206, 141, 220, 134, 65, 64, 143, 126, 202, 159, 115, 117, 169, 234, 216, 94, 114, 125, 233, 228, 28, 149, 132, 219, 119, 235, 119, 2, 17, 0, 0, 0, 1, 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