Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bf011526e11a3b53aa1853e51c867d12c91a7e80d2a109b0c235e845e56d0b6

Tx prefix hash: 555d45a5a9103e9c7eea261fb6ff510422613e64eed1163fe0a83c736e163b11
Tx public key: 66f24b6b3ad985d88d9424e101098ba120318b4efb7bbaed324c3ad08fb54269
Timestamp: 1712012128 Timestamp [UCT]: 2024-04-01 22:55:28 Age [y:d:h:m:s]: 01:244:09:16:26
Block: 991300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433408 RingCT/type: yes/0
Extra: 0166f24b6b3ad985d88d9424e101098ba120318b4efb7bbaed324c3ad08fb5426902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df51e75a17acb4d999808b35a49335435e6be51a3f3ed1b200a1b71c16a71f9c 0.600000000000 1451634 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": 991310, "vin": [ { "gen": { "height": 991300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df51e75a17acb4d999808b35a49335435e6be51a3f3ed1b200a1b71c16a71f9c" } } ], "extra": [ 1, 102, 242, 75, 107, 58, 217, 133, 216, 141, 148, 36, 225, 1, 9, 139, 161, 32, 49, 139, 78, 251, 123, 186, 237, 50, 76, 58, 208, 143, 181, 66, 105, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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