Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeee722146b2140087229b6877d1e9c73eba9f71959ac7ac696a59e316ca277b

Tx prefix hash: 3810a971f1daa82bd58c394b88e5f5ff6c150c90f63b701e3fbbf784c91e5ca9
Tx public key: 752682e82e40b557b26d17380f0e94b7eb0b2f56cda305afebe1324d0c57d335
Timestamp: 1729601662 Timestamp [UCT]: 2024-10-22 12:54:22 Age [y:d:h:m:s]: 00:187:00:31:58
Block: 1137126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133484 RingCT/type: yes/0
Extra: 01752682e82e40b557b26d17380f0e94b7eb0b2f56cda305afebe1324d0c57d335021100000001a6b5e9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dc82d3490ab097a0a5be7e0a464afea39f20c7d143aa201fb11a2e9915e8db3 0.600000000000 1620559 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": 1137136, "vin": [ { "gen": { "height": 1137126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dc82d3490ab097a0a5be7e0a464afea39f20c7d143aa201fb11a2e9915e8db3" } } ], "extra": [ 1, 117, 38, 130, 232, 46, 64, 181, 87, 178, 109, 23, 56, 15, 14, 148, 183, 235, 11, 47, 86, 205, 163, 5, 175, 235, 225, 50, 77, 12, 87, 211, 53, 2, 17, 0, 0, 0, 1, 166, 181, 233, 251, 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