Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9e8316a8e40be6e19491cd546baa56f6cabed85aa06dae4574dbc11df59bf7

Tx prefix hash: 5821de246907e60ceaa86b50ffec5c1e3c84a57dcde2f0de1dc6aa0dd74fc7f4
Tx public key: d07fb0ae9c522fe6ef8727e02d320ef47efb753f8f97e29da32a5ebd89453df6
Timestamp: 1658870992 Timestamp [UCT]: 2022-07-26 21:29:52 Age [y:d:h:m:s]: 02:280:02:58:45
Block: 552380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721416 RingCT/type: yes/0
Extra: 01d07fb0ae9c522fe6ef8727e02d320ef47efb753f8f97e29da32a5ebd89453df602110000000175e3f0e9000000000000000000

1 output(s) for total of 9.072686093000 dcy

stealth address amount amount idx
00: 6f2423aa8c84e8f9e405959bb785b9d3f8981e2a72e0da722777ce33fbc1300d 9.072686093000 984082 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": 552390, "vin": [ { "gen": { "height": 552380 } } ], "vout": [ { "amount": 9072686093, "target": { "key": "6f2423aa8c84e8f9e405959bb785b9d3f8981e2a72e0da722777ce33fbc1300d" } } ], "extra": [ 1, 208, 127, 176, 174, 156, 82, 47, 230, 239, 135, 39, 224, 45, 50, 14, 244, 126, 251, 117, 63, 143, 151, 226, 157, 163, 42, 94, 189, 137, 69, 61, 246, 2, 17, 0, 0, 0, 1, 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