← previous blocknext block →recent activity
Analyzing
Block #87,715,154
29 transactions · 24 stateful · 2026-07-14 14:10:33 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,715,154 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w110w011w114w016w117w219w321w322w423w224w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb529f62…663c
0x34b655…2a6f
10 touches
10 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x388114fc…db6d
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
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
10 conflicts on slot 0xdb529f62fb…23663c
Audit this contract →
← previous block·next block →recent activity