← previous blocknext block →recent activity
Analyzing
Block #92,770,324
15 transactions · 14 stateful · 2026-08-03 12:06:22 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,770,324 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d6753e…a54e
0x34b655…2a6f
6 touches
3 conflicts
0x8c612cd4…59cc
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xa435dee8…f2be
0x34b655…2a6f
4 touches
1 conflict
0xcf827da3…f2a5
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x69d6753e0c…54a54e
Audit this contract →
← previous block·next block →recent activity