Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2d9aa84d74e724cf99495259ecb8c4220f5a57c895bd6759b3a2c382e1cf7e

Tx prefix hash: 13d9d811e8fbeb0684a7b0e9d7677558002a11c1a64bf459069bfb737a305995
Tx public key: 0a8d6c99561d75a920b75a37e2e63b365e51d42d41099a60e434ab0f71370516
Timestamp: 1710294080 Timestamp [UCT]: 2024-03-13 01:41:20 Age [y:d:h:m:s]: 01:026:13:14:41
Block: 977100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279954 RingCT/type: yes/0
Extra: 010a8d6c99561d75a920b75a37e2e63b365e51d42d41099a60e434ab0f713705160211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6362320fa6525bb09f0a14cf607051a79dddf1a767653172ef033992ef8363ce 0.600000000000 1437101 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": 977110, "vin": [ { "gen": { "height": 977100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6362320fa6525bb09f0a14cf607051a79dddf1a767653172ef033992ef8363ce" } } ], "extra": [ 1, 10, 141, 108, 153, 86, 29, 117, 169, 32, 183, 90, 55, 226, 230, 59, 54, 94, 81, 212, 45, 65, 9, 154, 96, 228, 52, 171, 15, 113, 55, 5, 22, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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