Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a790eefe5cb49e747287ffaa49f9bae5e26250c402eb9891a3995a0debf5eb8f

Tx prefix hash: b0edb56eb7ef169ce43dc53aea41431562825040a31043cd59f32903a467d555
Tx public key: fddbe5ea6f826231b1b07ed84e5ca29c32b2ae83c75613c61e27623abb57a05c
Timestamp: 1708596641 Timestamp [UCT]: 2024-02-22 10:10:41 Age [y:d:h:m:s]: 01:060:22:43:54
Block: 963014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304585 RingCT/type: yes/0
Extra: 01fddbe5ea6f826231b1b07ed84e5ca29c32b2ae83c75613c61e27623abb57a05c02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb6d7dd7facbf1ce58b664748f63f8a0d24f891cbd30f486971f36def2236fee 0.600000000000 1422711 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": 963024, "vin": [ { "gen": { "height": 963014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb6d7dd7facbf1ce58b664748f63f8a0d24f891cbd30f486971f36def2236fee" } } ], "extra": [ 1, 253, 219, 229, 234, 111, 130, 98, 49, 177, 176, 126, 216, 78, 92, 162, 156, 50, 178, 174, 131, 199, 86, 19, 198, 30, 39, 98, 58, 187, 87, 160, 92, 2, 17, 0, 0, 0, 12, 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