← previous blocknext block →recent activity
Analyzing
Block #89,701,109
11 transactions · 11 stateful · 2026-07-23 18:19:50 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,701,109 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b666394…cae1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6ccf5c86…9954
0x851145…3f07
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xded1a8af…e766
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x3b6663946d…4ecae1
Audit this contract →
← previous block·next block →recent activity