← previous blocknext block →recent activity
Analyzing
Block #87,726,307
20 transactions · 16 stateful · 2026-07-14 15:25:16 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,726,307 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w411w512w615w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x559bc887…2da8
0x34b655…2a6f
10 touches
10 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
10 touches
10 conflicts
0x6c2aa5be…d808
0x34b655…2a6f
10 touches
10 conflicts
0x5ec64628…72e4
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xad0c7701…1d83
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 0x559bc88742…032da8
Audit this contract →
← previous block·next block →recent activity