← previous blocknext block →recent activity
Analyzing
Block #92,853,765
11 transactions · 9 stateful · 2026-08-03 19:06:18 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,853,765 · 11 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1de366f5…69a3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x26784e10…ca1f
0x34b655…2a6f
2 touches
0 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
2 touches
0 conflicts
0x5701e33e…a3fe
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc1da8f73f5…20484c
Audit this contract →
← previous block·next block →recent activity