pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,972,225
← previous block
next block →
recent activity
Analyzing
Block #108,972,225
13 transactions · 10 stateful · 2026-09-29 07:05:14 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,972,225
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
#3
updatePrices
#4
0x5acec890
#5
0x5acec890
#6
updatePriceFeedsIfNecessary
#7
executeBatch
· blocks 1
#9
0xed82b078
#10
0xed82b078
#11
execFwdPositionOpsV2
#12
setData
#8
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x012b7b0e…16c4
0xe52b14…7230
3 touches
1 conflict
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
2 touches
0 conflicts
0x793357cd…1653
0x34b655…2a6f
2 touches
0 conflicts
0x88fc2a68…3918
0x34b655…2a6f
2 touches
0 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
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:
0xe52b1424…bb7230
1 conflict on slot
0x8ffa332881…c9ce11
Audit this contract →
← previous block
·
next block →
recent activity