Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79293c31ff9ed266a32a2407935ff9eb73ea8316ac1d3d6ebb0d43f3f8a7cc2c

Tx prefix hash: 48577a0c883ec39e8a2f3d5b81e655d9f032c6452cd6efb0d0aa5a8cab86d64b
Tx public key: 348f5f6c6442c9ac7ca5906a384852e029cb12858b92f5f6290254c01b23fa00
Timestamp: 1700803407 Timestamp [UCT]: 2023-11-24 05:23:27 Age [y:d:h:m:s]: 01:133:14:17:48
Block: 898398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356652 RingCT/type: yes/0
Extra: 01348f5f6c6442c9ac7ca5906a384852e029cb12858b92f5f6290254c01b23fa000211000000024b8f5122000000000000000000

1 output(s) for total of 0.647492093000 dcy

stealth address amount amount idx
00: 20d54ff8c074289a332fe0b5e0fb5931d043bb86b909d5a5b50ed8c3e79a2ed1 0.647492093000 1354811 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": 898408, "vin": [ { "gen": { "height": 898398 } } ], "vout": [ { "amount": 647492093, "target": { "key": "20d54ff8c074289a332fe0b5e0fb5931d043bb86b909d5a5b50ed8c3e79a2ed1" } } ], "extra": [ 1, 52, 143, 95, 108, 100, 66, 201, 172, 124, 165, 144, 106, 56, 72, 82, 224, 41, 203, 18, 133, 139, 146, 245, 246, 41, 2, 84, 192, 27, 35, 250, 0, 2, 17, 0, 0, 0, 2, 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