Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d91247f3fa45b7bf05ef6273e7e8229f46ea46e6808a29daab5f11af907cdcde

Tx prefix hash: e2942fc93e57a11ef85d8212f8c44ad832f51d26d7f8167a9def62b3045084b8
Tx public key: eaaadd7c38968cac3a2b85fd66271cf9f471930fb37596748c92b4c3fcb2a34d
Timestamp: 1712835258 Timestamp [UCT]: 2024-04-11 11:34:18 Age [y:d:h:m:s]: 01:034:04:47:14
Block: 998124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285443 RingCT/type: yes/0
Extra: 01eaaadd7c38968cac3a2b85fd66271cf9f471930fb37596748c92b4c3fcb2a34d02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86e7afa7ea67f40db523abc31b7fa2da9b3e09460f09ef3466ea16cabe40753c 0.600000000000 1458566 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": 998134, "vin": [ { "gen": { "height": 998124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86e7afa7ea67f40db523abc31b7fa2da9b3e09460f09ef3466ea16cabe40753c" } } ], "extra": [ 1, 234, 170, 221, 124, 56, 150, 140, 172, 58, 43, 133, 253, 102, 39, 28, 249, 244, 113, 147, 15, 179, 117, 150, 116, 140, 146, 180, 195, 252, 178, 163, 77, 2, 17, 0, 0, 0, 6, 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