← previous blocknext block →recent activity
Analyzing
Block #89,682,448
33 transactions · 30 stateful · 2026-07-23 16:45:44 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.64
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #89,682,448 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w110w013w014w115w216w317w418w519w620w721w823w126w330w231w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
18 touches
36 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810d
0x34b655…2a6f
6 touches
3 conflicts
0xba562b93…53fd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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: 0x48cba278…e2b48b
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity