← previous blocknext block →recent activity
Analyzing
Block #90,823,699
28 transactions · 21 stateful · 2026-07-27 16:50:06 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,823,699 · 28 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
1w06w07w18w210w011w112w213w314w216w017w120w321w424w025w126w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x401a563c…0ae7
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x401a563caa…1e0ae7
Audit this contract →
← previous block·next block →recent activity