← previous blocknext block →recent activity
Analyzing
Block #92,222,822
9 transactions · 8 stateful · 2026-08-01 14:11:33 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,222,822 · 9 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
1w03w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51ec09c…b4a9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x42b04648…21d1
0x34b655…2a6f
6 touches
3 conflicts
0x45f48a5c…0a93
0x34b655…2a6f
6 touches
3 conflicts
0x5b942246…89f0
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
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 0xf51ec09cc1…a1b4a9
Audit this contract →
← previous block·next block →recent activity