pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,614,580
← previous block
next block →
recent activity
Analyzing
Block #87,614,580
9 transactions · 7 stateful · 2026-07-14 02:57:59 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,614,580
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#4
setData
#7
0x6a55a62f
#8
0xb9ab36…b52d
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bce8fb9…edb6
0x34b655…2a6f
6 touches
3 conflicts
0xf0ad9713…5796
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8912
0x34b655…2a6f
4 touches
1 conflict
0xbbee202a…8913
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xdc94dccd…a653
0x34b655…2a6f
4 touches
1 conflict
0xdfd1344f…43f5
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
3 conflicts on slot
0x0bce8fb986…faedb6
Audit this contract →
← previous block
·
next block →
recent activity