← previous blocknext block →recent activity
Analyzing
Block #99,330,817
16 transactions · 16 stateful · 2026-08-26 12:37:45 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,330,817 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w28w39w410w412w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0x1e324eb6…34f0
0x34b655…2a6f
4 touches
1 conflict
0x1f314ff8…81c5
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x25180879…8191
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x3448c759…e6ba
0x34b655…2a6f
4 touches
1 conflict
0x3e01bb2b…00f4
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
3 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity