← previous blocknext block →recent activity
Analyzing
Block #89,541,857
25 transactions · 24 stateful · 2026-07-23 01:47:45 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,541,857 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w07w18w010w211w313w414w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x8df5fa2c…02e6
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x81066529…8924
0x34b655…2a6f
6 touches
3 conflicts
0xb7acd4ad…22ac
0xd32edf…ff58
5 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity