Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 158279015ccabcf46c04dff3c9c60d364c67c473c5deaafed63292d4ced3d451

Tx prefix hash: 8c9d5e675c1429234a3bd5144a3234c40cd49e55f86353f24dcad204be6053cc
Tx public key: e3242852d88376e5c72ae341a2999ff47f4a72f9d83b32162aa6d077daf06ccb
Timestamp: 1722432272 Timestamp [UCT]: 2024-07-31 13:24:32 Age [y:d:h:m:s]: 00:323:16:50:43
Block: 1077721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231157 RingCT/type: yes/0
Extra: 01e3242852d88376e5c72ae341a2999ff47f4a72f9d83b32162aa6d077daf06ccb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e90d1f839965b2df36fdaae280ec79067132e198dae6184e801c8e98b103809d 0.600000000000 1550276 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": 1077731, "vin": [ { "gen": { "height": 1077721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e90d1f839965b2df36fdaae280ec79067132e198dae6184e801c8e98b103809d" } } ], "extra": [ 1, 227, 36, 40, 82, 216, 131, 118, 229, 199, 42, 227, 65, 162, 153, 159, 244, 127, 74, 114, 249, 216, 59, 50, 22, 42, 166, 208, 119, 218, 240, 108, 203, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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