← previous blocknext block →recent activity
Analyzing
Block #91,409,830
50 transactions · 29 stateful · 2026-07-29 18:01:03 UTC
Parallelism
84/100
Blocked
62%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,409,830 · 50 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w112w217w018w121w222w328w029w130w231w332w134w135w436w440w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd2e35622…f491
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x41377979…0a18
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity