← previous blocknext block →recent activity
Analyzing
Block #89,542,828
18 transactions · 16 stateful · 2026-07-23 01:54:15 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,542,828 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w210w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x25810cd9…9b59
0x34b655…2a6f
6 touches
3 conflicts
0x2ee5c07b…7eb9
0x34b655…2a6f
6 touches
3 conflicts
0x3dc8ed8f…9df1
0x34b655…2a6f
6 touches
3 conflicts
0xe8e76b59…bc94
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity