← previous blocknext block →recent activity
Analyzing
Block #87,319,324
16 transactions · 11 stateful · 2026-07-12 18:02:35 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,319,324 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x3b552ea8…3a4b
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x79d50d4a…951d
0x34b655…2a6f
6 touches
3 conflicts
0x96047c45…b64a
0x34b655…2a6f
6 touches
3 conflicts
0xc368d7fd…aaec
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
3 conflicts on slot 0x3483ab79f0…398ed3
Audit this contract →
← previous block·next block →recent activity