← previous blocknext block →recent activity
Analyzing
Block #88,091,078
38 transactions · 38 stateful · 2026-07-16 08:05:06 UTC
Parallelism
47/100
Blocked
71%
Avg conflicts / tx
5.5
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #88,091,078 · 38 txs across 20 waves · depth 20
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
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w410w011w112w213w314w415w516w617w718w830w531w632w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
40 touches
190 conflicts
0x6cc0d35c…d162
0x0a2fbf…29b1
40 touches
190 conflicts
0x6cc0d35c…d163
0x0a2fbf…29b1
40 touches
190 conflicts
0xf0e9055b…d65c
0x0a2fbf…29b1
40 touches
190 conflicts
0xf0e9055b…d65d
0x0a2fbf…29b1
40 touches
190 conflicts
0xf0e9055b…d660
0x0a2fbf…29b1
40 touches
190 conflicts
0x00000000…0005
0x370e2e…63b4
40 touches
190 conflicts
0x1bff683e…7ecb
0x754704…b603
40 touches
190 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
190 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity