Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3a7317b420bc7612e3a08739a264a98fe7419cc56f9ccbf5a05564ae0ecc69

Tx prefix hash: 00856e4802cccf7d7bad5115170a8c7331283b14714a262fd172c44b36422212
Tx public key: e3a517b38a7baefa74c5f6e13a423d6ade9a612dfdc219712364baa35d1b305f
Timestamp: 1726490351 Timestamp [UCT]: 2024-09-16 12:39:11 Age [y:d:h:m:s]: 00:238:21:29:40
Block: 1111365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170586 RingCT/type: yes/0
Extra: 01e3a517b38a7baefa74c5f6e13a423d6ade9a612dfdc219712364baa35d1b305f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 257c19c4a00ffbc582ed8436ef4efdd7f48f186740d5650c5272de98673d3445 0.600000000000 1590296 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": 1111375, "vin": [ { "gen": { "height": 1111365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "257c19c4a00ffbc582ed8436ef4efdd7f48f186740d5650c5272de98673d3445" } } ], "extra": [ 1, 227, 165, 23, 179, 138, 123, 174, 250, 116, 197, 246, 225, 58, 66, 61, 106, 222, 154, 97, 45, 253, 194, 25, 113, 35, 100, 186, 163, 93, 27, 48, 95, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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