pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,754,662
← previous block
next block →
recent activity
Analyzing
Block #92,754,662
11 transactions · 11 stateful · 2026-08-03 10:47:32 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,754,662
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#8
commit
#9
setData
#10
0xc7e3ec2c
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e6ae5c2…0c94
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0x4c0627bd…f5c3
0x34b655…2a6f
4 touches
1 conflict
0xc80fe8da…c05d
0x34b655…2a6f
4 touches
1 conflict
0x4c0627bd…f5c4
0x34b655…2a6f
4 touches
1 conflict
0xca2926e0…61b5
0x34b655…2a6f
4 touches
1 conflict
0xe1b6b3c8…6676
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
0x1e6ae5c257…a60c94
Audit this contract →
← previous block
·
next block →
recent activity