← previous blocknext block →recent activity
Analyzing
Block #90,627,324
21 transactions · 20 stateful · 2026-07-27 00:22:05 UTC
Parallelism
52/100
Blocked
60%
Avg conflicts / tx
1.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #90,627,324 · 21 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
2w03w14w25w26w38w49w512w613w616w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe8d58d34…426d
0x34b655…2a6f
8 touches
6 conflicts
0xa9c9d8d8…e190
0x34b655…2a6f
6 touches
3 conflicts
0x0110331c…b891
0x34b655…2a6f
6 touches
3 conflicts
0x572da21f…f703
0x34b655…2a6f
6 touches
3 conflicts
0x53699236…fede
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity