← previous blocknext block →recent activity
Analyzing
Block #87,759,764
17 transactions · 16 stateful · 2026-07-14 19:09:03 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,759,764 · 17 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
1w04w05w16w27w39w010w211w312w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0x5597fdd8…3f39
0x34b655…2a6f
6 touches
3 conflicts
0x6611e109…e2b3
0x34b655…2a6f
6 touches
3 conflicts
0x323fde37…d7bc
0x34b655…2a6f
4 touches
1 conflict
0x43b8f3d9…ef28
0x34b655…2a6f
4 touches
1 conflict
0x6611e109…e2b2
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity