← previous blocknext block →recent activity
Analyzing
Block #92,221,312
11 transactions · 11 stateful · 2026-08-01 14:03:57 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,221,312 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a42683d…6f4f
0x34b655…2a6f
4 touches
1 conflict
0x0a42683d…6f50
0x34b655…2a6f
4 touches
1 conflict
0x1cd0ff28…1c1e
0x34b655…2a6f
4 touches
1 conflict
0x42dbb8c5…af52
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0x65d63aa3…d144
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0x0a42683dda…f36f4f
Audit this contract →
← previous block·next block →recent activity