← previous blocknext block →recent activity
Analyzing
Block #92,261,520
17 transactions · 15 stateful · 2026-08-01 17:26:11 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,261,520 · 17 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
2w03w14w05w16w27w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90d75b1f…1664
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x921067e6…525c
0x34b655…2a6f
6 touches
3 conflicts
0xf4da392f…8d43
0x34b655…2a6f
4 touches
1 conflict
0x5c90576a…ce6e
0x34b655…2a6f
4 touches
1 conflict
0x7d07e5f7…6703
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x9718c153…c410
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 0x90d75b1f3e…4c1664
Audit this contract →
← previous block·next block →recent activity