← previous blocknext block →recent activity
Analyzing
Block #99,875,914
25 transactions · 22 stateful · 2026-08-28 10:35:08 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,875,914 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w07w113w214w315w318w019w120w021w122w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x278603a8…d824
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0x272e6316…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
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
6 conflicts on slot 0x278603a849…e3d824
Audit this contract →
← previous block·next block →recent activity