← previous blocknext block →recent activity
Analyzing
Block #87,588,188
16 transactions · 16 stateful · 2026-07-14 00:01:29 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,588,188 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63dffde1…1765
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xb776c4e0…4e0a
0x34b655…2a6f
10 touches
10 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
10 touches
10 conflicts
0xad0c7701…1d83
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
8 touches
6 conflicts
0x48c8831b…dca0
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
10 conflicts on slot 0x63dffde1c2…ab1765
Audit this contract →
← previous block·next block →recent activity