Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ebc81086ea76e61eceb73738fd96923dc5f67910d5707336e320c20b1e22b01

Tx prefix hash: b9767fa644a8a98186026e06afa5647e1f5c54dcc200b3df1d217d9902ff23e7
Tx public key: 54992f826e8e7ca47fb9bdc33b32c167b3d24b27b5bf734ab988a601e55478ca
Timestamp: 1682229322 Timestamp [UCT]: 2023-04-23 05:55:22 Age [y:d:h:m:s]: 02:033:01:42:27
Block: 744664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545815 RingCT/type: yes/0
Extra: 0154992f826e8e7ca47fb9bdc33b32c167b3d24b27b5bf734ab988a601e55478ca02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.092277353000 dcy

stealth address amount amount idx
00: 8276f3d9f549b47889b39c0f6a69166480b4e3bbd9c36e0a455789909aa6abe1 2.092277353000 1192029 of 0

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": 744674, "vin": [ { "gen": { "height": 744664 } } ], "vout": [ { "amount": 2092277353, "target": { "key": "8276f3d9f549b47889b39c0f6a69166480b4e3bbd9c36e0a455789909aa6abe1" } } ], "extra": [ 1, 84, 153, 47, 130, 110, 142, 124, 164, 127, 185, 189, 195, 59, 50, 193, 103, 179, 210, 75, 39, 181, 191, 115, 74, 185, 136, 166, 1, 229, 84, 120, 202, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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