← previous blocknext block →recent activity
Analyzing
Block #89,698,278
33 transactions · 29 stateful · 2026-07-23 18:05:35 UTC
Parallelism
61/100
Blocked
72%
Avg conflicts / tx
2.91
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #89,698,278 · 33 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w39w410w011w112w213w314w415w516w617w718w819w925w527w628w631w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
26 touches
78 conflicts
0xc91796b2…1217
0x0a2fbf…29b1
26 touches
78 conflicts
0xc91796b2…1218
0x0a2fbf…29b1
26 touches
78 conflicts
0x00000000…0006
0x0a2fbf…29b1
26 touches
78 conflicts
0x89f9ad51…b081
0x0a2fbf…29b1
26 touches
78 conflicts
0x89f9ad51…b082
0x0a2fbf…29b1
26 touches
78 conflicts
0x89f9ad51…b085
0x0a2fbf…29b1
26 touches
78 conflicts
0x1bff683e…7ecb
0x754704…b603
26 touches
78 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: 0x370e2ee6…bd63b4
78 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity