Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32679c5c05360e604e47499c4de14f8b20f4bf2debdb6d6b1a77db6a79b1c30

Tx prefix hash: bb08872a7405fc776fba8b43cc924b9d166b74d2673b14235508159d5f382232
Tx public key: 91ae6f9cf5de6c9eb2f43ce152d8d44f0bf30b83903be0462591ccd6794e6266
Timestamp: 1726565049 Timestamp [UCT]: 2024-09-17 09:24:09 Age [y:d:h:m:s]: 00:201:17:35:01
Block: 1111977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143992 RingCT/type: yes/0
Extra: 0191ae6f9cf5de6c9eb2f43ce152d8d44f0bf30b83903be0462591ccd6794e626602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 122da1fbd686fdeca739ec0522da5ac83e1212e9f0a7616f84cae4d1b58e6f4f 0.600000000000 1591130 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": 1111987, "vin": [ { "gen": { "height": 1111977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "122da1fbd686fdeca739ec0522da5ac83e1212e9f0a7616f84cae4d1b58e6f4f" } } ], "extra": [ 1, 145, 174, 111, 156, 245, 222, 108, 158, 178, 244, 60, 225, 82, 216, 212, 79, 11, 243, 11, 131, 144, 59, 224, 70, 37, 145, 204, 214, 121, 78, 98, 102, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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