Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e6dc214ed2e94781f50943230919d6305533a7aaacaba216bbcc21b9681000

Tx prefix hash: 40e5735752f42e6d04326584fd10978183ed81004ce76fc4ef6307e98b8e0d1b
Tx public key: 4d656eed295bdb7f0b7097e18311e3e8c7a5e7b741baadcc893bd3d04e09db1c
Timestamp: 1676454733 Timestamp [UCT]: 2023-02-15 09:52:13 Age [y:d:h:m:s]: 01:336:06:56:24
Block: 697430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501300 RingCT/type: yes/0
Extra: 014d656eed295bdb7f0b7097e18311e3e8c7a5e7b741baadcc893bd3d04e09db1c021100000001faf35c9c000000000000000000

1 output(s) for total of 3.000054560000 dcy

stealth address amount amount idx
00: a337a4069395f9e72fec57fd5280d082bbab9651660a3e16dcc225934cb84c31 3.000054560000 1140603 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": 697440, "vin": [ { "gen": { "height": 697430 } } ], "vout": [ { "amount": 3000054560, "target": { "key": "a337a4069395f9e72fec57fd5280d082bbab9651660a3e16dcc225934cb84c31" } } ], "extra": [ 1, 77, 101, 110, 237, 41, 91, 219, 127, 11, 112, 151, 225, 131, 17, 227, 232, 199, 165, 231, 183, 65, 186, 173, 204, 137, 59, 211, 208, 78, 9, 219, 28, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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