← previous blocknext block →recent activity
Analyzing
Block #89,555,346
16 transactions · 14 stateful · 2026-07-23 03:17:54 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,555,346 · 16 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
1w07w08w19w210w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa3ec705f…b84f
0x34b655…2a6f
6 touches
3 conflicts
0x81dbafca…d1ea
0x851145…3f07
4 touches
1 conflict
0x9db3090e…7fb8
0x34b655…2a6f
4 touches
1 conflict
0xa97a87d3…264e
0x34b655…2a6f
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity