pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,211,057
← previous block
next block →
recent activity
Analyzing
Block #76,211,057
10 transactions · 7 stateful · 2026-05-22 06:55:41 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,211,057
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
setData
#6
0xc5a04723
#7
execOrders
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a672810…1732
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x18082983…b5f8
0x34b655…2a6f
4 touches
1 conflict
0x0b621a7d…2611
0x34b655…2a6f
2 touches
0 conflicts
0x1a44398b…cf39
0x34b655…2a6f
2 touches
0 conflicts
0x1be8019f…b769
0x34b655…2a6f
2 touches
0 conflicts
0x2b856d86…7988
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
0x7a6728105c…191732
Audit this contract →
← previous block
·
next block →
recent activity