pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,678,544
← previous block
next block →
recent activity
Analyzing
Block #90,678,544
11 transactions · 10 stateful · 2026-07-27 04:39:46 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,678,544
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x5a5d9a99
#3
setData
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
0xed82b078
#8
execOrders
#9
execOrders
#10
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce315079…6b83
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x01bad49a…5119
0x34b655…2a6f
2 touches
0 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x316f707b…07bc
0x34b655…2a6f
2 touches
0 conflicts
0x316f707b…07bd
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
0xce3150792b…4e6b83
Audit this contract →
← previous block
·
next block →
recent activity