← previous blocknext block →recent activity
Analyzing
Block #88,080,924
40 transactions · 36 stateful · 2026-07-16 06:57:11 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
1.93
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #88,080,924 · 40 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
1w02w13w27w19w210w311w012w113w015w016w117w218w319w420w524w125w226w427w328w529w331w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x5777bd87…71bd
0x34b655…2a6f
8 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0xe40c96f3…9ce4
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xff4a358a…762f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity