Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21aedaafe151b654d4fe7cd0a3b8de00d35c9af58b16d2ace96d2683211f1e1f

Tx prefix hash: 66ba3a86fe7b30c89d13f92c785d7f758dfe70f74890d2270bf0464972ea43dd
Tx public key: 3677a7eac8e98369e5ac17f60a69d1897f826a8fdb7f9d27f428fba253f12950
Timestamp: 1686043778 Timestamp [UCT]: 2023-06-06 09:29:38 Age [y:d:h:m:s]: 01:314:11:22:13
Block: 776286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485956 RingCT/type: yes/0
Extra: 013677a7eac8e98369e5ac17f60a69d1897f826a8fdb7f9d27f428fba253f1295002110000000275e3f0e9000000000000000000

1 output(s) for total of 1.643775091000 dcy

stealth address amount amount idx
00: 719eb8a4af6651cf4d1455c753a21f8b7bfa53770bb37f0e8955c3e2c6e4c2b0 1.643775091000 1225827 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": 776296, "vin": [ { "gen": { "height": 776286 } } ], "vout": [ { "amount": 1643775091, "target": { "key": "719eb8a4af6651cf4d1455c753a21f8b7bfa53770bb37f0e8955c3e2c6e4c2b0" } } ], "extra": [ 1, 54, 119, 167, 234, 200, 233, 131, 105, 229, 172, 23, 246, 10, 105, 209, 137, 127, 130, 106, 143, 219, 127, 157, 39, 244, 40, 251, 162, 83, 241, 41, 80, 2, 17, 0, 0, 0, 2, 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