Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31d98a53614dbd3143e1f90b5390d91b1ce1c751b58486dd5ba46859168b8156

Tx prefix hash: 75658538f845ca38d8f8a6e164b695e17e5b946cce0adf7139d72270ade5527f
Tx public key: 30c02c711e5d01c963f25330d684c0ec8a8f059df930e350cd430651443d0e00
Timestamp: 1723539801 Timestamp [UCT]: 2024-08-13 09:03:21 Age [y:d:h:m:s]: 00:246:11:41:38
Block: 1086906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176045 RingCT/type: yes/0
Extra: 0130c02c711e5d01c963f25330d684c0ec8a8f059df930e350cd430651443d0e00021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4404600c0e80f3c6e06a232ff35e4f65490f8f0f119dee1e4c16fdffc206aab 0.600000000000 1561505 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": 1086916, "vin": [ { "gen": { "height": 1086906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4404600c0e80f3c6e06a232ff35e4f65490f8f0f119dee1e4c16fdffc206aab" } } ], "extra": [ 1, 48, 192, 44, 113, 30, 93, 1, 201, 99, 242, 83, 48, 214, 132, 192, 236, 138, 143, 5, 157, 249, 48, 227, 80, 205, 67, 6, 81, 68, 61, 14, 0, 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