Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e7b323905cb454aaa7475a14e410f13f49552774ba85bfc812807689bb0c7c1

Tx prefix hash: e8b92c921cb2b3a67fea7b96f48241c7cccc2090833cf1e02f86ace4a46f4587
Tx public key: 02967c8696909378abf8e9ca4bb4b0e513d1685b9ac0466f4f4e4aaf392ea1ce
Timestamp: 1695790739 Timestamp [UCT]: 2023-09-27 04:58:59 Age [y:d:h:m:s]: 01:196:17:50:54
Block: 857046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401672 RingCT/type: yes/0
Extra: 0102967c8696909378abf8e9ca4bb4b0e513d1685b9ac0466f4f4e4aaf392ea1ce02110000000c4b8f5122000000000000000000

1 output(s) for total of 0.887668629000 dcy

stealth address amount amount idx
00: 5f6324c7f2b5b30dc40f6fe16ae09a29ad3d46c3b5828c0e7e8476ade6f8cb16 0.887668629000 1311148 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": 857056, "vin": [ { "gen": { "height": 857046 } } ], "vout": [ { "amount": 887668629, "target": { "key": "5f6324c7f2b5b30dc40f6fe16ae09a29ad3d46c3b5828c0e7e8476ade6f8cb16" } } ], "extra": [ 1, 2, 150, 124, 134, 150, 144, 147, 120, 171, 248, 233, 202, 75, 180, 176, 229, 19, 209, 104, 91, 154, 192, 70, 111, 79, 78, 74, 175, 57, 46, 161, 206, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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