pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,922,590
← previous block
next block →
recent activity
Analyzing
Block #100,922,590
11 transactions · 11 stateful · 2026-09-01 02:26:49 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,922,590
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
· blocks 1
#3
0x5acec890
#5
0x5acec890
#6
0x59558d29
#8
updateDataFeedsValuesPartial
#9
0x6a963861
#10
setData
#4
0x5acec890
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3ca276c8…3dfc
0x34b655…2a6f
2 touches
0 conflicts
0x3e1b21c6…b1e4
0x34b655…2a6f
2 touches
0 conflicts
0x4ebc22e7…0702
0x34b655…2a6f
2 touches
0 conflicts
0x51134e2a…e079
0x34b655…2a6f
2 touches
0 conflicts
0x537b38ff…2c21
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:
Perpl
1 conflict on slot
0xdc9915b513…2b542c
Audit this contract →
← previous block
·
next block →
recent activity