← previous blocknext block →recent activity
Analyzing
Block #89,514,844
17 transactions · 14 stateful · 2026-07-22 22:47:21 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,514,844 · 17 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
5w08w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x0a2ca0ad…6411
0x0a2fbf…29b1
10 touches
10 conflicts
0x0a2ca0ad…6412
0x0a2fbf…29b1
10 touches
10 conflicts
0x0a2ca0ad…6415
0x0a2fbf…29b1
10 touches
10 conflicts
0x55b4e430…44cb
0x754704…b603
10 touches
10 conflicts
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4a
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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity