← previous blocknext block →recent activity
Analyzing
Block #95,246,120
39 transactions · 30 stateful · 2026-08-12 04:01:29 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.49
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #95,246,120 · 39 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w29w310w416w217w318w519w622w725w626w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x49611dcc…9864
0x34b655…2a6f
10 touches
10 conflicts
0xa5e2fdd2…a81b
0x34b655…2a6f
8 touches
6 conflicts
0xb2699a97…9c44
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xe7bd356d…d23a
0x34b655…2a6f
8 touches
6 conflicts
0xe7bd356d…d23b
0x34b655…2a6f
8 touches
6 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: Perpl
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity