← previous blocknext block →recent activity
Analyzing
Block #87,593,382
20 transactions · 18 stateful · 2026-07-14 00:36:13 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,593,382 · 20 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
1w04w05w16w27w38w410w511w612w114w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x34d95d94…3a16
0x34b655…2a6f
6 touches
3 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
6 touches
3 conflicts
0x5e3a31d1…7a6e
0x34b655…2a6f
6 touches
3 conflicts
0x689d5e98…d068
0x34b655…2a6f
6 touches
3 conflicts
0x70040326…40e5
0x34b655…2a6f
6 touches
3 conflicts
0x875164c2…f8a2
0x34b655…2a6f
6 touches
3 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity