← previous blocknext block →recent activity
Analyzing
Block #95,349,896
62 transactions · 56 stateful · 2026-08-12 12:50:52 UTC
Parallelism
65/100
Blocked
82%
Avg conflicts / tx
3.26
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #95,349,896 · 62 txs across 22 waves · depth 22
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w07w38w49w110w211w345w147w348w449w550w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
14 touches
21 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xeae24c72…e30be0
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity