← previous blocknext block →recent activity
Analyzing
Block #91,825,971
25 transactions · 23 stateful · 2026-07-31 04:55:26 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,825,971 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w08w210w311w412w513w114w218w019w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2da3a8ad…628d
0x34b655…2a6f
4 touches
1 conflict
0x2da3a8ad…628e
0x34b655…2a6f
4 touches
1 conflict
0x301fa4c6…73db
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 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity