← previous blocknext block →recent activity
Analyzing
Block #87,753,964
20 transactions · 18 stateful · 2026-07-14 18:30:17 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,753,964 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w29w310w411w512w213w314w416w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x3e8b3a49…53ee
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xb8a51c40…3d5d
0x34b655…2a6f
8 touches
6 conflicts
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 conflicts
0x44d2a1cc…5e3e
0x34b655…2a6f
6 touches
3 conflicts
0x648bb928…97f2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity