pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,934,743
← previous block
next block →
recent activity
Analyzing
Block #101,934,743
7 transactions · 7 stateful · 2026-09-04 15:20:55 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,934,743
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
#4
setData
#5
execOrders
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74b835e1…b1bd
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x12449483…9cff
0x34b655…2a6f
2 touches
0 conflicts
0x1533d8bf…585a
0x34b655…2a6f
2 touches
0 conflicts
0x1c3c5667…bca1
0x34b655…2a6f
2 touches
0 conflicts
0x1cae0ea1…6152
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
0x74b835e15e…e9b1bd
Audit this contract →
← previous block
·
next block →
recent activity