← previous blocknext block →recent activity
Analyzing
Block #90,823,289
16 transactions · 15 stateful · 2026-07-27 16:48:02 UTC
Parallelism
44/100
Blocked
67%
Avg conflicts / tx
1.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #90,823,289 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w610w611w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xbd6941a1…6281
0x34b655…2a6f
6 touches
3 conflicts
0x58d6b9cf…7c9e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0x526c671d…6f90
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity