pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,522,297
← previous block
next block →
recent activity
Analyzing
Block #85,522,297
10 transactions · 10 stateful · 2026-07-04 10:00:51 UTC
Parallelism
60
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,522,297
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xaf5e395a
#2
0xab083028
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
setData
#9
0xc7e3ec2c
#6
execOrders
· blocks 2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0x9916a36a…514d
0x34b655…2a6f
4 touches
1 conflict
0x5b4cd072…c461
0x3bd359…433a
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
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