← previous blocknext block →recent activity
Analyzing
Block #92,865,115
18 transactions · 17 stateful · 2026-08-03 20:03:27 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,865,115 · 18 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
1w04w06w17w18w09w112w213w315w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bbd28c…e227
0x34b655…2a6f
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x57b02276…db3f
0x34b655…2a6f
6 touches
3 conflicts
0x6459805c…615d
0x34b655…2a6f
6 touches
3 conflicts
0x97785d36…2ac5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x15c22181…1354
0x34b655…2a6f
5 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
3 conflicts on slot 0x00bbd28c94…39e227
Audit this contract →
← previous block·next block →recent activity