← previous blocknext block →recent activity
Analyzing
Block #90,791,304
27 transactions · 22 stateful · 2026-07-27 14:07:02 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,791,304 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w07w111w013w114w215w219w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xe8d58d34…426d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0a005879…de60
0x34b655…2a6f
6 touches
3 conflicts
0x731e3928…350e
0xd32edf…ff58
5 touches
3 conflicts
0x30685372…8f8d
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity