← previous blocknext block →recent activity
Analyzing
Block #92,177,354
14 transactions · 11 stateful · 2026-08-01 10:22:55 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,177,354 · 14 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
2w04w05w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eb410fd…591d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa53250c9…f399
0x34b655…2a6f
6 touches
3 conflicts
0xd0a08c81…bdbf
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x17abd0b1…f478
0x34b655…2a6f
4 touches
1 conflict
0x2979e2dd…335e
0x34b655…2a6f
4 touches
1 conflict
0xf007a4f4…507d
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 0x1eb410fdc2…cd591d
Audit this contract →
← previous block·next block →recent activity