← previous blocknext block →recent activity
Analyzing
Block #91,959,829
40 transactions · 32 stateful · 2026-07-31 16:08:53 UTC
Parallelism
82/100
Blocked
56%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,959,829 · 40 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w010w011w112w013w114w215w316w422w324w126w327w428w530w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
10 touches
10 conflicts
0x3de775b2…319b
0xa6afd3…d132
10 touches
10 conflicts
0xfa551be3…a911
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x02991b41…19e6
0x34b655…2a6f
8 touches
6 conflicts
0xab5344c9…3de7
0x34b655…2a6f
8 touches
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity