← previous blocknext block →recent activity
Analyzing
Block #87,724,214
21 transactions · 20 stateful · 2026-07-14 15:11:16 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,724,214 · 21 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
2w03w14w05w16w27w38w49w511w213w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x3d381afb…8207
0x34b655…2a6f
10 touches
10 conflicts
0x79bdf655…91f2
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x709b98ea…4187
0x34b655…2a6f
8 touches
6 conflicts
0x7a7fd287…0637
0x34b655…2a6f
8 touches
6 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
8 touches
6 conflicts
0xb11a3969…fc6a
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity