← previous blocknext block →recent activity
Analyzing
Block #99,316,767
10 transactions · 9 stateful · 2026-08-26 11:27:05 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,316,767 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ff808a1…865f
0x34b655…2a6f
4 touches
1 conflict
0x73a116c5…6b8f
0x34b655…2a6f
4 touches
1 conflict
0x7e4547a3…c7d0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8b2b7213…4899
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x398d31f8…a8d8
0x34b655…2a6f
2 touches
0 conflicts
0x62910921…3016
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 0x1ff808a1c9…31865f
Audit this contract →
← previous block·next block →recent activity