Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d17d7a441be27b4e323070aa973f83596548e60375873c0efa0e58c6250d040

Tx prefix hash: 28336720aa383de45894efaa5c925af3fcffcdc0be8b154873cc1a57eca89a7f
Tx public key: e61c55a8f415ec61224677aa9cd07c3628d608fc550fcac99cf5d24d654f24d6
Timestamp: 1721976796 Timestamp [UCT]: 2024-07-26 06:53:16 Age [y:d:h:m:s]: 00:306:13:27:49
Block: 1073935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219061 RingCT/type: yes/0
Extra: 01e61c55a8f415ec61224677aa9cd07c3628d608fc550fcac99cf5d24d654f24d6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43f257ab97bab4f47a342c0ba6016e9477dc9b13a951f09cc55c3b2b238a0e10 0.600000000000 1546444 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": 1073945, "vin": [ { "gen": { "height": 1073935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43f257ab97bab4f47a342c0ba6016e9477dc9b13a951f09cc55c3b2b238a0e10" } } ], "extra": [ 1, 230, 28, 85, 168, 244, 21, 236, 97, 34, 70, 119, 170, 156, 208, 124, 54, 40, 214, 8, 252, 85, 15, 202, 201, 156, 245, 210, 77, 101, 79, 36, 214, 2, 17, 0, 0, 0, 1, 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