Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b55a389e8f56af7f0c48d756655b40cdc50bb4c5ec74f58c92183b85bb8fe22

Tx prefix hash: d14666649612efab21f2abc79a4aa2e18e9511d9ce95f8bda09c11098db8a1a9
Tx public key: 25800009abcd67af8b5c3c39d71695c25786fdb34aa9e30e9d732fa7a561443b
Timestamp: 1705860240 Timestamp [UCT]: 2024-01-21 18:04:00 Age [y:d:h:m:s]: 01:105:06:24:50
Block: 940300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336353 RingCT/type: yes/0
Extra: 0125800009abcd67af8b5c3c39d71695c25786fdb34aa9e30e9d732fa7a561443b02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07da48c2faf8fbe0deab1f1c06e96a9da2dc11954d5f09488bcef00c2885f4c9 0.600000000000 1398436 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": 940310, "vin": [ { "gen": { "height": 940300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07da48c2faf8fbe0deab1f1c06e96a9da2dc11954d5f09488bcef00c2885f4c9" } } ], "extra": [ 1, 37, 128, 0, 9, 171, 205, 103, 175, 139, 92, 60, 57, 215, 22, 149, 194, 87, 134, 253, 179, 74, 169, 227, 14, 157, 115, 47, 167, 165, 97, 68, 59, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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