← previous blocknext block →recent activity
Analyzing
Block #91,086,105
39 transactions · 34 stateful · 2026-07-28 14:51:06 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1.15
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,086,105 · 39 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w211w312w414w517w719w120w222w323w430w631w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc6b1d981…1be2
0xa6afd3…d132
8 touches
6 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0x49b8ccf1…2dd6
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity