Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426ca3a17caa33f6e55caefff2d7ef0de7fb3e4a1bb6b336791b9c7fe36838be

Tx prefix hash: a6af425a88865e2eb00473e7d32d934f95ae7caa70efb0ae050139b2934ab842
Tx public key: 82881dd5dff31496f7403830e8487de4cfa66ef9b15070f01bb8cf0c721eb5e8
Timestamp: 1682858786 Timestamp [UCT]: 2023-04-30 12:46:26 Age [y:d:h:m:s]: 01:343:22:43:50
Block: 749893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507058 RingCT/type: yes/0
Extra: 0182881dd5dff31496f7403830e8487de4cfa66ef9b15070f01bb8cf0c721eb5e8021100000002b3164c24000000000000000000

1 output(s) for total of 2.010450566000 dcy

stealth address amount amount idx
00: d19d25100ecdbc750eac045482b02445c38e78238abf6fb9fab2c21f15efc398 2.010450566000 1197912 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": 749903, "vin": [ { "gen": { "height": 749893 } } ], "vout": [ { "amount": 2010450566, "target": { "key": "d19d25100ecdbc750eac045482b02445c38e78238abf6fb9fab2c21f15efc398" } } ], "extra": [ 1, 130, 136, 29, 213, 223, 243, 20, 150, 247, 64, 56, 48, 232, 72, 125, 228, 207, 166, 110, 249, 177, 80, 112, 240, 27, 184, 207, 12, 114, 30, 181, 232, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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