pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,581,333
← previous block
next block →
recent activity
Analyzing
Block #92,581,333
11 transactions · 10 stateful · 2026-08-02 20:14:37 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,581,333
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x3f5c179b
#4
execOrders
· blocks 3
#7
execOrders
#9
0x59558d29
#10
0xc7e3ec2c
#5
execOrders
· blocks 2
#6
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0x9feb7f16…58ee
0x34b655…2a6f
4 touches
1 conflict
0xa4631748…0876
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x2a1086da…dba7
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
6 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity