← previous blocknext block →recent activity
Analyzing
Block #96,625,543
26 transactions · 21 stateful · 2026-08-16 23:51:20 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,625,543 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w210w011w114w315w016w017w118w221w422w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d31edd8…81c6
0x34b655…2a6f
8 touches
6 conflicts
0x36743f6f…476b
0x3bd359…433a
8 touches
6 conflicts
0x368be579…0623
0xd32edf…ff58
7 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x6d31edd87c…9e81c6
Audit this contract →
← previous block·next block →recent activity