← previous blocknext block →recent activity
Analyzing
Block #96,598,078
18 transactions · 18 stateful · 2026-08-16 21:33:12 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,598,078 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w210w311w412w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ab6fca5…de5c
0x34b655…2a6f
6 touches
3 conflicts
0x7f63a266…68c0
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x15c5e060…7c06
0x34b655…2a6f
4 touches
1 conflict
0x2a8b202d…3f70
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x39126904…24d8
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x9ab6fca525…66de5c
Audit this contract →
← previous block·next block →recent activity