← previous blocknext block →recent activity
Analyzing
Block #96,795,816
31 transactions · 25 stateful · 2026-08-17 14:07:44 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,795,816 · 31 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
1w02w03w14w15w27w08w112w113w214w218w323w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1cc9519…84c1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x03aa8b26…118a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf57da309…1d72
0x34b655…2a6f
6 touches
3 conflicts
0x1fd98771…f62e
0x34b655…2a6f
6 touches
3 conflicts
0x725005f3…5b0e
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 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
6 conflicts on slot 0xf1cc9519e3…fe84c1
Audit this contract →
← previous block·next block →recent activity