← previous blocknext block →recent activity
Analyzing
Block #96,603,139
10 transactions · 9 stateful · 2026-08-16 21:58:39 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,603,139 · 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
1w02w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb96d00bc…8144
0x34b655…2a6f
4 touches
1 conflict
0xd5d0b681…ca6c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x05ff217d…c411
0x34b655…2a6f
2 touches
0 conflicts
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x1a69c7c5…09cc
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 0xb96d00bca0…438144
Audit this contract →
← previous block·next block →recent activity