← previous blocknext block →recent activity
Analyzing
Block #91,249,488
22 transactions · 21 stateful · 2026-07-29 04:33:04 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
1.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,249,488 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w07w09w010w112w213w414w315w316w117w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe0e2eb39…0245
0x34b655…2a6f
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity