← previous blocknext block →recent activity
Analyzing
Block #92,768,516
20 transactions · 17 stateful · 2026-08-03 11:57:17 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,768,516 · 20 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
2w04w16w19w210w013w214w315w116w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x0395f77a…39bb
0x34b655…2a6f
6 touches
3 conflicts
0x7b80de04…86d1
0x34b655…2a6f
6 touches
3 conflicts
0xbb609115…3f96
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe5a38e46…a68c
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 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity