← previous blocknext block →recent activity
Analyzing
Block #90,449,985
12 transactions · 11 stateful · 2026-07-26 09:29:58 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,449,985 · 12 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
3w04w15w26w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x07e62691…ad33
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfd446…43f8
0x34b655…2a6f
2 touches
0 conflicts
0x5177b5c6…b946
0x34b655…2a6f
2 touches
0 conflicts
0x5bc6b706…fce6
0x34b655…2a6f
2 touches
0 conflicts
0x63b74d88…b6ca
0x34b655…2a6f
2 touches
0 conflicts
0x7150753f…7e32
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity