← previous blocknext block →recent activity
Analyzing
Block #92,410,963
13 transactions · 11 stateful · 2026-08-02 05:57:45 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,410,963 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eb410fd…591d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0x3f33f55b…32cb
0x34b655…2a6f
4 touches
1 conflict
0x67fcb980…c1bd
0x34b655…2a6f
4 touches
1 conflict
0x6b778857…f22f
0x34b655…2a6f
4 touches
1 conflict
0x6c1a3292…bd2c
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