Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73fd0297b95c4b1e3430aafa8d96c98c12029de0452966bc69f9f3a161a2a652

Tx prefix hash: 8d7da2901cadad04bbce55ecb42b71e0fda96c28521f01d5ae35e0d8e8839d09
Tx public key: f1adfed3c5d7989b7391b5625b9e17889ecdbc37e61ab23d9347477b531d829d
Timestamp: 1735368021 Timestamp [UCT]: 2024-12-28 06:40:21 Age [y:d:h:m:s]: 00:081:04:10:29
Block: 1184838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57817 RingCT/type: yes/0
Extra: 01f1adfed3c5d7989b7391b5625b9e17889ecdbc37e61ab23d9347477b531d829d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fee351da309b866ad06e2e67a1e49bb7e664897a9bfcfee0df88c4b8b000209 0.600000000000 1671297 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": 1184848, "vin": [ { "gen": { "height": 1184838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fee351da309b866ad06e2e67a1e49bb7e664897a9bfcfee0df88c4b8b000209" } } ], "extra": [ 1, 241, 173, 254, 211, 197, 215, 152, 155, 115, 145, 181, 98, 91, 158, 23, 136, 158, 205, 188, 55, 230, 26, 178, 61, 147, 71, 71, 123, 83, 29, 130, 157, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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