← previous blocknext block →recent activity
Analyzing
Block #91,208,772
30 transactions · 25 stateful · 2026-07-29 01:08:11 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,208,772 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w111w312w421w423w524w625w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x54d68470…4b32
0x34b655…2a6f
8 touches
6 conflicts
0xfee9c1d5…61d6
0x34b655…2a6f
7 touches
6 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity