Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e098d330f4924f67e2a60a28e8dcaf8fa692928679dba53097f225f81695d2e

Tx prefix hash: 955b2643865248ed116a0038eb4cda6be7de1beb7adff08059f83b8cbec97a27
Tx public key: 8697592841849934462a5bd796c7e5aa6ffa0a549d1043b2f6dfeb0d6f6a17ed
Timestamp: 1702628435 Timestamp [UCT]: 2023-12-15 08:20:35 Age [y:d:h:m:s]: 01:111:16:27:58
Block: 913533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340958 RingCT/type: yes/0
Extra: 018697592841849934462a5bd796c7e5aa6ffa0a549d1043b2f6dfeb0d6f6a17ed02110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cee7e8d3e86e89a68dcf0312e53c95984fe8342cf4225292a1705ebff66ba864 0.600000000000 1370805 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": 913543, "vin": [ { "gen": { "height": 913533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cee7e8d3e86e89a68dcf0312e53c95984fe8342cf4225292a1705ebff66ba864" } } ], "extra": [ 1, 134, 151, 89, 40, 65, 132, 153, 52, 70, 42, 91, 215, 150, 199, 229, 170, 111, 250, 10, 84, 157, 16, 67, 178, 246, 223, 235, 13, 111, 106, 23, 237, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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