← previous blocknext block →recent activity
Analyzing
Block #99,455,991
15 transactions · 14 stateful · 2026-08-26 23:08:08 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,455,991 · 15 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
3w04w05w16w28w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd4e3bc…d657
0x34b655…2a6f
6 touches
3 conflicts
0x359866c7…de7b
0x34b655…2a6f
6 touches
3 conflicts
0xcf11cf1a…ec04
0x34b655…2a6f
6 touches
3 conflicts
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
0x34b655…2a6f
2 touches
0 conflicts
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
2 touches
0 conflicts
0xbd22d0fc…64fd
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 0xfcd4e3bc6b…bed657
Audit this contract →
← previous block·next block →recent activity