← previous blocknext block →recent activity
Analyzing
Block #87,712,219
23 transactions · 23 stateful · 2026-07-14 13:50:53 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,712,219 · 23 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
1w02w13w04w25w36w47w511w412w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c2aa5be…d808
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x0ba865dd…a249
0x34b655…2a6f
8 touches
6 conflicts
0x21e1427f…8d09
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x74fd0a9b…3aaa
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 0x6c2aa5be8b…b1d808
Audit this contract →
← previous block·next block →recent activity