← previous blocknext block →recent activity
Analyzing
Block #91,412,100
26 transactions · 22 stateful · 2026-07-29 18:12:31 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.31
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,412,100 · 26 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
1w05w06w17w18w29w312w413w514w620w021w622w723w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfed09e59…a493
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity