← previous blocknext block →recent activity
Analyzing
Block #99,972,280
23 transactions · 19 stateful · 2026-08-28 18:40:44 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,972,280 · 23 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
1w02w13w24w07w19w010w113w214w017w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x6dedaff6…161b
0x34b655…2a6f
6 touches
3 conflicts
0x508441d8…0322
0xd32edf…ff58
5 touches
3 conflicts
0x0f842156…3a92
0x34b655…2a6f
4 touches
2 conflicts
0xba5743c7…21c1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x10d9e927…8179
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity