Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f4e4f2247fef282c2dd506f12c20e9f66c87ba88f2fa984f8312016d3a13e43

Tx prefix hash: d7fa25b06065b45a310cccce151ee1c8f7d8f6982784f59f8936839947e72f9a
Tx public key: f9705fcfb9e2daf4a4ab672ae50ab85cd0d07fb378a295ab53359f4bcceb720f
Timestamp: 1711627366 Timestamp [UCT]: 2024-03-28 12:02:46 Age [y:d:h:m:s]: 01:237:04:14:54
Block: 988154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428188 RingCT/type: yes/0
Extra: 01f9705fcfb9e2daf4a4ab672ae50ab85cd0d07fb378a295ab53359f4bcceb720f0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8146d19abd807ce2e11ccf8da1bd79e80946212d0f501679a9334d511a29bfeb 0.600000000000 1448421 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": 988164, "vin": [ { "gen": { "height": 988154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8146d19abd807ce2e11ccf8da1bd79e80946212d0f501679a9334d511a29bfeb" } } ], "extra": [ 1, 249, 112, 95, 207, 185, 226, 218, 244, 164, 171, 103, 42, 229, 10, 184, 92, 208, 208, 127, 179, 120, 162, 149, 171, 83, 53, 159, 75, 204, 235, 114, 15, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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