← previous blocknext block →recent activity
Analyzing
Block #87,637,265
21 transactions · 19 stateful · 2026-07-14 05:29:42 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,637,265 · 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
2w03w14w05w16w27w38w410w011w112w214w319w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed59b1cd…8509
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0xd8675136…9a01
0x34b655…2a6f
10 touches
10 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
10 touches
10 conflicts
0xd19c9d38…b459
0x34b655…2a6f
10 touches
10 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
10 touches
10 conflicts
0x8981596f…d14a
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
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 0xed59b1cd08…c98509
Audit this contract →
← previous block·next block →recent activity