pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,298,607
← previous block
next block →
recent activity
Analyzing
Block #95,298,607
7 transactions · 4 stateful · 2026-08-12 08:31:03 UTC
Parallelism
71
/100
Blocked
25
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,298,607
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xee83e0a5
#2
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x54f51f…9900
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb416438e…796a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6e689c48…a06b
0x34b655…2a6f
4 touches
1 conflict
0x2181fc88…19ad
0x928dc8…8207
2 touches
0 conflicts
0x33110615…9e9e
0x928dc8…8207
2 touches
0 conflicts
0x373a7308…c13e
0x928dc8…8207
2 touches
0 conflicts
0x44817e53…32d0
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
0xb416438e1c…17796a
Audit this contract →
← previous block
·
next block →
recent activity