← previous blocknext block →recent activity
Analyzing
Block #92,320,302
8 transactions · 7 stateful · 2026-08-01 22:21:50 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,320,302 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6153fb59…b910
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x47e8e44e…b446
0x34b655…2a6f
4 touches
1 conflict
0xd89b8bba…6cd4
0x34b655…2a6f
4 touches
1 conflict
0xd89b8bba…6cd5
0x34b655…2a6f
4 touches
1 conflict
0xf602d792…83e1
0x34b655…2a6f
3 touches
1 conflict
0x36da12cd…371e
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity