pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,112,448
← previous block
next block →
recent activity
Analyzing
Block #92,112,448
10 transactions · 9 stateful · 2026-08-01 04:56:27 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,112,448
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x39435dac
· blocks 1
#5
0x0f6795d9
· blocks 1
#6
setData
#8
0x94defb17
#9
0x59558d29
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd861b911…7b42
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x3a22223a…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x43e15ca4…039d
0x34b655…2a6f
2 touches
0 conflicts
0x45f48a5c…0a93
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
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
0xd861b9119d…dc7b42
Audit this contract →
← previous block
·
next block →
recent activity