← previous blocknext block →recent activity
Analyzing
Block #96,543,335
10 transactions · 7 stateful · 2026-08-16 16:57:51 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,543,335 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc1b52d3…76b9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x17fddaa0…8fa3
0x34b655…2a6f
2 touches
0 conflicts
0x1fa4bbc6…20ea
0x34b655…2a6f
2 touches
0 conflicts
0x2ac796c1…5bbc
0x34b655…2a6f
2 touches
0 conflicts
0x2b96d534…b6b5
0x34b655…2a6f
2 touches
0 conflicts
0x559b3e1a…9b8f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xcc1b52d315…6576b9
Audit this contract →
← previous block·next block →recent activity