← previous blocknext block →recent activity
Analyzing
Block #90,797,277
35 transactions · 26 stateful · 2026-07-27 14:37:05 UTC
Parallelism
86/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,797,277 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w319w320w022w423w125w126w227w328w029w130w231w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
10 touches
10 conflicts
0xb566cc65…214d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x28c714d9…9438
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5c16527f…628c
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: 0x80c74517…647210
10 conflicts on slot 0x0000000000…00004b
Audit this contract →
← previous block·next block →recent activity