← previous blocknext block →recent activity
Analyzing
Block #87,725,313
19 transactions · 17 stateful · 2026-07-14 15:18:36 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,725,313 · 19 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
2w03w14w25w36w47w59w210w311w612w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x2f35c56f…046b
0x34b655…2a6f
8 touches
6 conflicts
0xd526c4bd…dbf2
0x34b655…2a6f
6 touches
3 conflicts
0xc4de6652…13f4
0x34b655…2a6f
6 touches
3 conflicts
0x263aa68b…6c6a
0x34b655…2a6f
4 touches
1 conflict
0x28c62bca…b746
0x34b655…2a6f
4 touches
1 conflict
0x3d381afb…8207
0x34b655…2a6f
4 touches
1 conflict
0x4cdf55e1…0f2d
0x34b655…2a6f
4 touches
1 conflict
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity