← previous blocknext block →recent activity
Analyzing
Block #96,022,885
19 transactions · 19 stateful · 2026-08-14 21:19:51 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,022,885 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w06w07w18w19w013w214w315w416w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
10 touches
10 conflicts
0xa2f4cdc6…95be
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1a2055c7…9054
0x34b655…2a6f
6 touches
3 conflicts
0xa7865bef…7707
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0xe9ff451d…a2ee
0x34b655…2a6f
5 touches
3 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
10 conflicts on slot 0xa3a621f8f3…6975a2
Audit this contract →
← previous block·next block →recent activity