← previous blocknext block →recent activity
Analyzing
Block #96,325,717
9 transactions · 9 stateful · 2026-08-15 22:43:03 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,325,717 · 9 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
2w04w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x651d4cdd…66a6
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a7
0x34b655…2a6f
4 touches
1 conflict
0x81238469…de5d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xf287e8ea…19b1
0x34b655…2a6f
4 touches
1 conflict
0xf9e6d0fb…3651
0x34b655…2a6f
4 touches
1 conflict
0x28f3c4a3…6d6c
0x34b655…2a6f
2 touches
0 conflicts
0x48d4896a…d0c6
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 0x651d4cddab…b766a6
Audit this contract →
← previous block·next block →recent activity