← previous blocknext block →recent activity
Analyzing
Block #88,359,448
47 transactions · 35 stateful · 2026-07-17 14:01:08 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
1.89
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #88,359,448 · 47 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
5w06w18w09w110w211w012w114w021w022w123w224w325w426w527w628w729w830w931w234w735w837w145w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xd5ab2f5b…092b
0x34b655…2a6f
10 touches
10 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0x940159d0…2d61
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity