pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,833,920
← previous block
next block →
recent activity
Analyzing
Block #91,833,920
10 transactions · 10 stateful · 2026-07-31 05:35:25 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,833,920
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
0x6a6c3495
#8
setData
#9
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cc
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cd
0x34b655…2a6f
4 touches
1 conflict
0xacf40f57…c279
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf238796…545f
0x34b655…2a6f
4 touches
1 conflict
0xf30b9357…2e1e
0x34b655…2a6f
4 touches
1 conflict
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity