Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c16c70f762810d840232afebddc927a57fb758f2f9f53d1cc63d107270502d

Tx prefix hash: 2832bc5acd7417573de511a2cca98f4fa1afcfa7918bc9acd022dd3f2b20876a
Tx public key: e80bb8b52f1b97cf7d7c17b25c6180ee83d0ef9b72dd49e8e4844e240f762830
Timestamp: 1698330278 Timestamp [UCT]: 2023-10-26 14:24:38 Age [y:d:h:m:s]: 01:182:17:43:30
Block: 878121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391612 RingCT/type: yes/0
Extra: 01e80bb8b52f1b97cf7d7c17b25c6180ee83d0ef9b72dd49e8e4844e240f7628300211000000034b8f5122000000000000000000

1 output(s) for total of 0.755823894000 dcy

stealth address amount amount idx
00: d2274ffa9e47c70152eb9909dd2441a7af790f7005643d1673666a3248bc0f4b 0.755823894000 1333535 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": 878131, "vin": [ { "gen": { "height": 878121 } } ], "vout": [ { "amount": 755823894, "target": { "key": "d2274ffa9e47c70152eb9909dd2441a7af790f7005643d1673666a3248bc0f4b" } } ], "extra": [ 1, 232, 11, 184, 181, 47, 27, 151, 207, 125, 124, 23, 178, 92, 97, 128, 238, 131, 208, 239, 155, 114, 221, 73, 232, 228, 132, 78, 36, 15, 118, 40, 48, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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