← previous blocknext block →recent activity
Analyzing
Block #90,890,467
31 transactions · 31 stateful · 2026-07-27 22:26:01 UTC
Parallelism
52/100
Blocked
61%
Avg conflicts / tx
2.58
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #90,890,467 · 31 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w07w18w29w310w411w512w613w716w817w921w1122w1223w124w125w826w1327w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
10 touches
10 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity