Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a924e8b9263c291987b35e03459521b7d02086d0edb662565d6a7546b96d74f

Tx prefix hash: fc3480f91779a96ae321a1a044763f49f4c5a6dc89105641e4a773c26e9041cd
Tx public key: b42a378d6a78b36a86099610a649f03344be52c6e59b8b1cbe61bdddd3fa8489
Timestamp: 1577052585 Timestamp [UCT]: 2019-12-22 22:09:45 Age [y:d:h:m:s]: 05:081:07:49:46
Block: 29757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207729 RingCT/type: yes/0
Extra: 01b42a378d6a78b36a86099610a649f03344be52c6e59b8b1cbe61bdddd3fa84890211000000184943cd9f000000000000000000

1 output(s) for total of 489.106651463000 dcy

stealth address amount amount idx
00: e6a9927bbe34a0c9458967b9a0ff7767321050116a27f4959691ca7f443a630a 489.106651463000 49023 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": 29767, "vin": [ { "gen": { "height": 29757 } } ], "vout": [ { "amount": 489106651463, "target": { "key": "e6a9927bbe34a0c9458967b9a0ff7767321050116a27f4959691ca7f443a630a" } } ], "extra": [ 1, 180, 42, 55, 141, 106, 120, 179, 106, 134, 9, 150, 16, 166, 73, 240, 51, 68, 190, 82, 198, 229, 155, 139, 28, 190, 97, 189, 221, 211, 250, 132, 137, 2, 17, 0, 0, 0, 24, 73, 67, 205, 159, 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