← previous blocknext block →recent activity
Analyzing
Block #96,016,918
8 transactions · 7 stateful · 2026-08-14 20:49:50 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,016,918 · 8 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
1w02w13w25w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dca726c…af0b
0x34b655…2a6f
4 touches
1 conflict
0x82f1549d…82c3
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x065edde0…73a8
0x34b655…2a6f
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x2fc3ae85…2555
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 0x8dca726cd3…2faf0b
Audit this contract →
← previous block·next block →recent activity