← previous blocknext block →recent activity
Analyzing
Block #91,070,032
39 transactions · 33 stateful · 2026-07-28 13:30:11 UTC
Parallelism
62/100
Blocked
67%
Avg conflicts / tx
2.54
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #91,070,032 · 39 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w39w011w112w013w114w215w316w417w518w619w720w821w924w429w230w334w1235w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xafb8e71e…9285
0x34b655…2a6f
10 touches
10 conflicts
0x957c875f…b3f9
0x34b655…2a6f
10 touches
10 conflicts
0xf1345bef…5530
0x34b655…2a6f
10 touches
10 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
8 touches
6 conflicts
0x8047e9b2…9bb8
0x34b655…2a6f
8 touches
6 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity