pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,981,988
← previous block
next block →
recent activity
Analyzing
Block #91,981,988
11 transactions · 8 stateful · 2026-07-31 18:00:20 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,981,988
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x38ae9ef8
· blocks 1
#3
harvest
#4
executeBatch
#5
0x3f5c179b
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x59558d29
#2
0x8f9ad8be
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dca7cdd…b416
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0xdece3ef2…f62f
0x188d58…ea8e
2 touches
0 conflicts
0x0677a587…9f1d
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:
0x928dc8af…fd8207
1 conflict on slot
0x8dca7cddbf…48b416
Audit this contract →
← previous block
·
next block →
recent activity