← previous blocknext block →recent activity
Analyzing
Block #92,760,933
16 transactions · 14 stateful · 2026-08-03 11:19:06 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,760,933 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w49w511w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca2926e0…61b5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
2 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x04717fc0…1cf7
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
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
6 conflicts on slot 0xca2926e0af…1961b5
Audit this contract →
← previous block·next block →recent activity