← previous blocknext block →recent activity
Analyzing
Block #90,651,249
24 transactions · 23 stateful · 2026-07-27 02:22:27 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #90,651,249 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w512w513w614w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfc3d5171…8357
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5f79e36a…edf9
0x34b655…2a6f
6 touches
3 conflicts
0x72b220d0…c85d
0x34b655…2a6f
6 touches
3 conflicts
0x72c8aeb2…9921
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity