← previous blocknext block →recent activity
Analyzing
Block #89,748,641
11 transactions · 10 stateful · 2026-07-23 22:19:50 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,748,641 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5625ec2a…00f2
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x17a61f90…3c73
0x34b655…2a6f
2 touches
0 conflicts
0x22c6ecc6…c70d
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x3c0e0a72…deff
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
1 conflict on slot 0x7f63a2661a…b468c0
Audit this contract →
← previous block·next block →recent activity