← previous blocknext block →recent activity
Analyzing
Block #88,354,897
44 transactions · 36 stateful · 2026-07-17 13:30:22 UTC
Parallelism
68/100
Blocked
72%
Avg conflicts / tx
1.82
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #88,354,897 · 44 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w08w113w014w115w216w317w418w519w620w722w723w826w227w128w329w931w432w534w1038w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xebac0f82…a49c
0x34b655…2a6f
8 touches
6 conflicts
0x5f707cb3…648e
0x34b655…2a6f
8 touches
6 conflicts
0xf565ea1f…4245
0x34b655…2a6f
8 touches
6 conflicts
0x0ca3397e…3644
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity