← previous blocknext block →recent activity
Analyzing
Block #90,803,258
22 transactions · 19 stateful · 2026-07-27 15:07:11 UTC
Parallelism
82/100
Blocked
58%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,803,258 · 22 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
1w02w13w04w06w17w08w19w210w312w213w214w316w118w019w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0x1a8f5c7d…854b
0x34b655…2a6f
4 touches
1 conflict
0x33819f63…2104
0x34b655…2a6f
4 touches
1 conflict
0x364289f7…f98a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x806bf739…e950
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity