← previous blocknext block →recent activity
Analyzing
Block #91,126,082
23 transactions · 19 stateful · 2026-07-28 18:12:14 UTC
Parallelism
78/100
Blocked
58%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,126,082 · 23 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
1w02w13w04w15w06w17w28w311w212w014w115w216w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity