← previous blocknext block →recent activity
Analyzing
Block #90,794,393
21 transactions · 19 stateful · 2026-07-27 14:22:34 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,794,393 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w310w311w413w514w618w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x53699236…fede
0x34b655…2a6f
6 touches
3 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
4 touches
1 conflict
0x5ee667a1…2a60
0x34b655…2a6f
4 touches
1 conflict
0x62389136…5c8f
0x34b655…2a6f
4 touches
1 conflict
0x6b0d2ce5…ff19
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity