← previous blocknext block →recent activity
Analyzing
Block #88,352,695
27 transactions · 25 stateful · 2026-07-17 13:15:31 UTC
Parallelism
33/100
Blocked
72%
Avg conflicts / tx
5.7
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #88,352,695 · 27 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1419w1520w1621w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x370e2e…63b4
36 touches
153 conflicts
0x55b4e430…44cb
0x754704…b603
36 touches
153 conflicts
0x1bff683e…7ecb
0x754704…b603
36 touches
153 conflicts
0x00000000…0006
0x0a2fbf…29b1
36 touches
153 conflicts
0x09e18d72…4a27
0x0a2fbf…29b1
36 touches
153 conflicts
0x09e18d72…4a28
0x0a2fbf…29b1
36 touches
153 conflicts
0x09e18d72…4a2b
0x0a2fbf…29b1
36 touches
153 conflicts
0xb5b74228…2144
0x0a2fbf…29b1
36 touches
153 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
153 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity