← previous blocknext block →recent activity
Analyzing
Block #90,975,836
17 transactions · 17 stateful · 2026-07-28 05:35:27 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,975,836 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8e3540b1…3a9a
0x34b655…2a6f
6 touches
3 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
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: Perpl
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity