← previous blocknext block →recent activity
Analyzing
Block #90,803,874
30 transactions · 27 stateful · 2026-07-27 15:10:17 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
1.57
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #90,803,874 · 30 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w09w010w111w212w313w414w515w616w718w126w927w1028w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x5c16527f…628c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3e403ed4…f52b
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0x9bab29d4…da69
0xd32edf…ff58
5 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity