← previous blocknext block →recent activity
Analyzing
Block #88,364,493
73 transactions · 66 stateful · 2026-07-17 14:35:06 UTC
Parallelism
74/100
Blocked
73%
Avg conflicts / tx
4.37
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #88,364,493 · 73 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w48w59w610w711w812w148w549w151w657w958w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
38 touches
171 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
18 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 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
171 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity