← previous blocknext block →recent activity
Analyzing
Block #90,790,747
13 transactions · 13 stateful · 2026-07-27 14:04:14 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,790,747 · 13 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
1w03w14w25w06w37w48w111w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x326bbf43…df3d
0x34b655…2a6f
6 touches
3 conflicts
0xc7b1189e…d092
0x34b655…2a6f
6 touches
3 conflicts
0x114324a9…6d5e
0x34b655…2a6f
6 touches
3 conflicts
0x76df3cf6…c8d1
0x34b655…2a6f
4 touches
1 conflict
0x78b60ad8…8468
0x34b655…2a6f
4 touches
1 conflict
0x9e25632f…f25b
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity