pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,577,537
← previous block
next block →
recent activity
Analyzing
Block #89,577,537
12 transactions · 11 stateful · 2026-07-23 05:46:08 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,577,537
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0x3f5c179b
#7
executeBatch
#8
0x6a61ab17
#9
0x0cf032c6
#10
setData
#11
0x39435dac
#2
matchOrders
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd3d49b7…23bc
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x85dc2524…53bc
0x754704…b603
4 touches
1 conflict
0x90942247…f5cb
0x754704…b603
4 touches
1 conflict
0x33951a20…e93c
0x34b655…2a6f
2 touches
0 conflicts
0x4bd66377…f067
0x34b655…2a6f
2 touches
0 conflicts
0x5f394770…ac95
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:
USDC (USDC)
1 conflict on slot
0xfd3d49b7a4…0f23bc
Audit this contract →
← previous block
·
next block →
recent activity