pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,771,119
← previous block
next block →
recent activity
Analyzing
Block #91,771,119
7 transactions · 7 stateful · 2026-07-31 00:19:29 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,771,119
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
execOrders
#4
batchUpdatePrice
#5
setData
#6
0xc7e3ec2c
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3586d447…a796
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x10379e8d…3675
0x34b655…2a6f
2 touches
0 conflicts
0x1ca9a6de…019e
0x34b655…2a6f
2 touches
0 conflicts
0x310afe2c…83e1
0x34b655…2a6f
2 touches
0 conflicts
0x3b666394…cae1
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
0x3586d44724…2da796
Audit this contract →
← previous block
·
next block →
recent activity