← previous blocknext block →recent activity
Analyzing
Block #91,269,068
48 transactions · 46 stateful · 2026-07-29 06:11:54 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
1.77
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,269,068 · 48 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w39w410w516w117w218w324w125w426w527w628w730w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65c5c2dc…cdde
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xefcdf197…96a2
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
8 touches
6 conflicts
0xa501ec94…c718
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
21 conflicts on slot 0x65c5c2dca1…fccdde
Audit this contract →
← previous block·next block →recent activity