← previous blocknext block →recent activity
Analyzing
Block #91,063,705
25 transactions · 21 stateful · 2026-07-28 12:58:21 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,063,705 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w010w011w112w013w216w317w118w121w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbeac3b7…c14b
0x34b655…2a6f
8 touches
6 conflicts
0x28c438ba…31f1
0x065c9d…c394
4 touches
1 conflict
0x013a6b08…d120
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
6 conflicts on slot 0xbbeac3b703…d0c14b
Audit this contract →
← previous block·next block →recent activity