← previous blocknext block →recent activity
Analyzing
Block #99,618,200
27 transactions · 24 stateful · 2026-08-27 12:51:04 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,618,200 · 27 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
1w02w15w06w07w112w213w214w016w018w119w120w022w324w025w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fce7a05…d778
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd76853e9…cd23
0x34b655…2a6f
6 touches
3 conflicts
0x1d682814…3e90
0xd32edf…ff58
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x554873fd…2ff4
0x34b655…2a6f
4 touches
1 conflict
0xfaf5fe80…1ffc
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 0x6fce7a0516…35d778
Audit this contract →
← previous block·next block →recent activity