← previous blocknext block →recent activity
Analyzing
Block #89,784,868
16 transactions · 15 stateful · 2026-07-24 01:22:45 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,784,868 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w110w212w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0004
0x158622…375e
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0x1d5181ef…7074
0x34b655…2a6f
4 touches
1 conflict
0xb47de4be…f8bd
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity