pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,253,292
← previous block
next block →
recent activity
Analyzing
Block #93,253,292
7 transactions · 7 stateful · 2026-08-05 04:37:13 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
#93,253,292
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePosition
#3
execFwdPositionOps
· blocks 1
#5
setData
#6
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x0b87b350…991f
0x6657d1…8ccc
2 touches
0 conflicts
0x2cea0b7d…0c24
0x6657d1…8ccc
2 touches
0 conflicts
0x2e64a4ea…fd79
0x6657d1…8ccc
2 touches
0 conflicts
0x46488d16…2467
0x6657d1…8ccc
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
0xe0e0068315…bbe335
Audit this contract →
← previous block
·
next block →
recent activity