← previous blocknext block →recent activity
Analyzing
Block #96,623,011
11 transactions · 8 stateful · 2026-08-16 23:38:36 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,623,011 · 11 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
5w06w17w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdbe6b59…f6d8
0x34b655…2a6f
6 touches
3 conflicts
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
2 touches
0 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
2 touches
0 conflicts
0xa5811d93…8c73
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
3 conflicts on slot 0xbdbe6b59da…0cf6d8
Audit this contract →
← previous block·next block →recent activity