← previous blocknext block →recent activity
Analyzing
Block #88,191,337
55 transactions · 49 stateful · 2026-07-16 19:16:37 UTC
Parallelism
67/100
Blocked
73%
Avg conflicts / tx
4
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #88,191,337 · 55 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
1w02w13w25w09w112w213w314w415w516w617w718w819w944w1048w152w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
36 touches
153 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x3464bbc5…a323
0xa6afd3…d132
12 touches
15 conflicts
0x1803586e…d149
0xa6afd3…d132
12 touches
15 conflicts
0xdb067026…9eb8
0x2b46c0…1669
10 touches
10 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
10 touches
10 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: 0x48cba278…e2b48b
153 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity