← previous blocknext block →recent activity
Analyzing
Block #91,417,539
106 transactions · 59 stateful · 2026-07-29 18:39:53 UTC
Parallelism
82/100
Blocked
76%
Avg conflicts / tx
1.81
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #91,417,539 · 106 txs across 19 waves · depth 19
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
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w08w116w017w119w021w122w224w342w145w248w349w450w553w656w763w288w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
18 touches
36 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…641f
0x34b655…2a6f
12 touches
15 conflicts
0x84d6407e…6fb2
0x34b655…2a6f
12 touches
15 conflicts
0x40ee7a94…d6a8
0x34b655…2a6f
12 touches
15 conflicts
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0x542ff3d0…3fa7
0x34b655…2a6f
12 touches
15 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity