← previous blocknext block →recent activity
Analyzing
Block #90,772,846
14 transactions · 13 stateful · 2026-07-27 12:34:08 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,772,846 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w08w19w110w211w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0014a3c…77c6
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0x24eaf46d…8c2e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcd9e7f41…edca
0x34b655…2a6f
6 touches
3 conflicts
0xe833d959…8666
0x34b655…2a6f
6 touches
3 conflicts
0x4b8cad87…ef1a
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
3 conflicts on slot 0xa0014a3c86…5377c6
Audit this contract →
← previous block·next block →recent activity