← previous blocknext block →recent activity
Analyzing
Block #89,570,104
17 transactions · 16 stateful · 2026-07-23 04:56:30 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,570,104 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w29w311w312w414w015w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fbd24c7…325b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
6 touches
3 conflicts
0x81e1b637…2b3b
0x34b655…2a6f
6 touches
3 conflicts
0x81e1b637…2b3c
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
6 touches
3 conflicts
0xaca60768…7272
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
10 conflicts on slot 0x1fbd24c7f5…59325b
Audit this contract →
← previous block·next block →recent activity