← previous blocknext block →recent activity
Analyzing
Block #88,359,134
48 transactions · 38 stateful · 2026-07-17 13:59:02 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.67
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #88,359,134 · 48 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
2w03w110w012w013w116w018w119w020w121w222w323w424w525w626w729w430w234w136w839w242w943w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x2f461725…5ab2
0x34b655…2a6f
10 touches
10 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
10 touches
10 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0x34b222ef…4afc
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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