Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e39237b2aad2ff847555364b7f2a9d2911a1d999968420987cd342b0cb39bfb7

Tx prefix hash: 27c75552f5cdfb9aa3fe8355e3e251827d345742a2085fccec08403b2b3d4b89
Tx public key: f25e8ca9ccac1cf5341e681717d41e25b0b3b699e527a358004c2393cee582c0
Timestamp: 1716959313 Timestamp [UCT]: 2024-05-29 05:08:33 Age [y:d:h:m:s]: 00:307:07:22:25
Block: 1032347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219623 RingCT/type: yes/0
Extra: 01f25e8ca9ccac1cf5341e681717d41e25b0b3b699e527a358004c2393cee582c002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1318b686fd1840f72e642004df15b857143fa856fbc791d7f665b20a79ea54ba 0.600000000000 1500800 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": 1032357, "vin": [ { "gen": { "height": 1032347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1318b686fd1840f72e642004df15b857143fa856fbc791d7f665b20a79ea54ba" } } ], "extra": [ 1, 242, 94, 140, 169, 204, 172, 28, 245, 52, 30, 104, 23, 23, 212, 30, 37, 176, 179, 182, 153, 229, 39, 163, 88, 0, 76, 35, 147, 206, 229, 130, 192, 2, 17, 0, 0, 0, 7, 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