pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,176,263
← previous block
next block →
recent activity
Analyzing
Block #92,176,263
9 transactions · 9 stateful · 2026-08-01 10:17:26 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,176,263
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
approve
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#8
0x59558d29
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bea6eae…9f7b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x083ff337…401b
0x34b655…2a6f
2 touches
0 conflicts
0x0856447c…3acb
0x34b655…2a6f
2 touches
0 conflicts
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x24223eb9…13ba
0x34b655…2a6f
2 touches
0 conflicts
0x30ccc990…afe5
0x34b655…2a6f
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
0x2bea6eae34…b89f7b
Audit this contract →
← previous block
·
next block →
recent activity