← previous blocknext block →recent activity
Analyzing
Block #96,261,752
10 transactions · 9 stateful · 2026-08-15 17:21:20 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,261,752 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0a255626…48e1
0x34b655…2a6f
2 touches
0 conflicts
0x109ba141…437f
0x34b655…2a6f
2 touches
0 conflicts
0x17a14264…f419
0x34b655…2a6f
2 touches
0 conflicts
0x2f4b1dc8…e9fa
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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 0x4a39a2a411…a6857b
Audit this contract →
← previous block·next block →recent activity