← previous blocknext block →recent activity
Analyzing
Block #99,870,325
23 transactions · 22 stateful · 2026-08-28 10:07:00 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,870,325 · 23 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
2w08w19w013w115w017w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x96ed54e2…04ed
0x34b655…2a6f
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x89aa48d2…1244
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity