← previous blocknext block →recent activity
Analyzing
Block #88,340,332
18 transactions · 16 stateful · 2026-07-17 11:52:49 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,340,332 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w212w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x68b16879…8f0a
0x0a2fbf…29b1
6 touches
3 conflicts
0x68b16879…8f0b
0x0a2fbf…29b1
6 touches
3 conflicts
0x68b16879…8f0e
0x0a2fbf…29b1
6 touches
3 conflicts
0xd33d5c8d…5ecc
0x0a2fbf…29b1
6 touches
3 conflicts
0xd33d5c8d…5ecd
0x0a2fbf…29b1
6 touches
3 conflicts
0x2004b5f1…ff98
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity