← previous blocknext block →recent activity
Analyzing
Block #90,208,526
20 transactions · 16 stateful · 2026-07-25 13:00:07 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,208,526 · 20 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
1w03w04w15w06w27w18w315w416w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x78346476…4311
0x34b655…2a6f
8 touches
6 conflicts
0xbeed7137…b58e
0x34b655…2a6f
8 touches
6 conflicts
0x18316bb4…d507
0x34b655…2a6f
6 touches
3 conflicts
0x3eede796…d745
0x34b655…2a6f
6 touches
3 conflicts
0xda515b01…4dbf
0x34b655…2a6f
6 touches
3 conflicts
0x121b4bfb…7677
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity