pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,277,658
← previous block
next block →
recent activity
Analyzing
Block #95,277,658
10 transactions · 10 stateful · 2026-08-12 06:45:18 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,277,658
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x38ae9ef8
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#9
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x730c8155…0856
0x34b655…2a6f
4 touches
1 conflict
0x8faba3a7…8454
0x34b655…2a6f
4 touches
1 conflict
0xd6255b52…69e7
0x34b655…2a6f
4 touches
1 conflict
0x72da4494…8b2f
0x34b655…2a6f
4 touches
1 conflict
0x3afdcde6…1651
0x928dc8…8207
2 touches
0 conflicts
0x613560f2…8d9e
0x928dc8…8207
2 touches
0 conflicts
0x6ea637c9…dce9
0x928dc8…8207
2 touches
0 conflicts
0x6ea637c9…dcea
0x928dc8…8207
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
0x730c81554f…1e0856
Audit this contract →
← previous block
·
next block →
recent activity