← previous blocknext block →recent activity
Analyzing
Block #88,355,418
45 transactions · 40 stateful · 2026-07-17 13:33:52 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
1.96
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #88,355,418 · 45 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w211w012w113w014w115w216w317w418w519w620w725w626w727w228w129w332w333w434w238w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
10 touches
10 conflicts
0x02991b41…19e6
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6c45a31…9931
0x34b655…2a6f
6 touches
3 conflicts
0xf565ea1f…4245
0x34b655…2a6f
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity