← previous blocknext block →recent activity
Analyzing
Block #92,061,140
10 transactions · 9 stateful · 2026-08-01 00:38:25 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,061,140 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b778857…f22f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x1f02e5b0…3439
0x34b655…2a6f
2 touches
0 conflicts
0x279ddfdc…78fb
0x34b655…2a6f
2 touches
0 conflicts
0x279ddfdc…78fc
0x34b655…2a6f
2 touches
0 conflicts
0x70a7b5d6…fe0e
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 0x6b77885710…95f22f
Audit this contract →
← previous block·next block →recent activity