← previous blocknext block →recent activity
Analyzing
Block #89,547,084
21 transactions · 20 stateful · 2026-07-23 02:22:41 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,547,084 · 21 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
6w09w010w111w212w314w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x238962d8…0fe2
0x0a2fbf…29b1
8 touches
6 conflicts
0x238962d8…0fe3
0x0a2fbf…29b1
8 touches
6 conflicts
0x238962d8…0fe6
0x0a2fbf…29b1
8 touches
6 conflicts
0x8cc2514d…e29f
0x0a2fbf…29b1
8 touches
6 conflicts
0x8cc2514d…e2a0
0x0a2fbf…29b1
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 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: 0x0a2fbf2d…f729b1
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity