← previous blocknext block →recent activity
Analyzing
Block #99,288,892
17 transactions · 17 stateful · 2026-08-26 09:06:52 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,288,892 · 17 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
3w06w07w113w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d6a99f9…da64
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x90f65937…f295
0x34b655…2a6f
4 touches
1 conflict
0x26471102…35f9
0x34b655…2a6f
2 touches
0 conflicts
0x280aaa58…1c52
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 0x9d6a99f99b…bfda64
Audit this contract →
← previous block·next block →recent activity