← previous blocknext block →recent activity
Analyzing
Block #96,653,875
10 transactions · 10 stateful · 2026-08-17 02:13:50 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,653,875 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56b390b…e0ce
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x6b63921e…7352
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x433ec3a1…a1e8
0x34b655…2a6f
2 touches
0 conflicts
0x58888587…bb8d
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
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 0xc56b390bd8…6be0ce
Audit this contract →
← previous block·next block →recent activity