pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,819,498
← previous block
next block →
recent activity
Analyzing
Block #90,819,498
9 transactions · 9 stateful · 2026-07-27 16:28:58 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,819,498
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x29eed2d3
#4
0xc5a04723
#5
0x6a6787c2
#6
setData
#8
0xc7e3ec2c
#2
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb9129e1…30b0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0xd877e706…e9c0
0x34b655…2a6f
4 touches
1 conflict
0x00d398c1…252a
0x34b655…2a6f
2 touches
0 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x049aaec3…6e5e
0x34b655…2a6f
2 touches
0 conflicts
0x0adf48a7…c84a
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
0xeb9129e1c7…c430b0
Audit this contract →
← previous block
·
next block →
recent activity