← previous blocknext block →recent activity
Analyzing
Block #87,662,663
20 transactions · 14 stateful · 2026-07-14 08:19:20 UTC
Parallelism
70/100
Blocked
36%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,662,663 · 20 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
4w07w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0804b2ba…8a77
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0bce8fb9…edb6
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x2ae834f7…a036
0x34b655…2a6f
6 touches
3 conflicts
0x68bec689…fccd
0x34b655…2a6f
6 touches
3 conflicts
0x6dcb5d8d…5f07
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 0x0804b2ba81…208a77
Audit this contract →
← previous block·next block →recent activity