← previous blocknext block →recent activity
Analyzing
Block #91,064,236
25 transactions · 23 stateful · 2026-07-28 13:01:02 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,064,236 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w09w110w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d1352cf…a515
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x251e4ed8…a3f4
0x34b655…2a6f
4 touches
1 conflict
0xd0de3ae7…fd2c
0x065c9d…c394
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 0x3d1352cf02…2ba515
Audit this contract →
← previous block·next block →recent activity