pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,892,862
← previous block
next block →
recent activity
Analyzing
Block #83,892,862
10 transactions · 9 stateful · 2026-06-26 21:00:19 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,892,862
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39abec6b
#2
0xed82b078
#3
updateDataFeedsValuesPartial
#4
0x6a3ee8db
#5
setData
#6
execOrders
· blocks 2
#9
0xc7e3ec2c
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
4 touches
1 conflict
0x1b4a1e84…42b8
0x34b655…2a6f
4 touches
1 conflict
0x92e4a5ce…7cec
0x34b655…2a6f
4 touches
1 conflict
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0x15a8b5e6…0296
0x2ab50b…5c41
2 touches
0 conflicts
0x1a9f8402…cd56
0x2ab50b…5c41
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity