← previous blocknext block →recent activity
Analyzing
Block #91,139,014
22 transactions · 21 stateful · 2026-07-28 19:17:17 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,139,014 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w311w212w313w414w315w520w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0xddfe6e94…d48b
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x2b69443e…c28f
0x34b655…2a6f
6 touches
3 conflicts
0x72470f81…c402
0x34b655…2a6f
4 touches
1 conflict
0x85c5eb6b…b05a
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 0xc0eb79d1cb…5529a4
Audit this contract →
← previous block·next block →recent activity