← previous blocknext block →recent activity
Analyzing
Block #99,850,531
17 transactions · 16 stateful · 2026-08-28 08:27:08 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,850,531 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w311w412w515w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
10 touches
10 conflicts
0x9d7f7621…97de
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0x82e3cbaa…ae67
0x065c9d…c394
4 touches
1 conflict
0x02803960…b9c0
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
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 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity