pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,513,938
← previous block
next block →
recent activity
Analyzing
Block #87,513,938
9 transactions · 8 stateful · 2026-07-13 15:44:11 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,513,938
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x3f5c179b
#8
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8085
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0x5d3732fe…b4bd
0x34b655…2a6f
4 touches
1 conflict
0xf69bf8bb…421f
0x34b655…2a6f
4 touches
1 conflict
0xf7af8195…cea4
0x34b655…2a6f
4 touches
1 conflict
0xa3441b92…521c
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0003
0x5afd3e…7620
2 touches
0 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
1 conflict on slot
0xf60d3c8069…62c8a7
Audit this contract →
← previous block
·
next block →
recent activity