pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,894,422
← previous block
next block →
recent activity
Analyzing
Block #101,894,422
10 transactions · 9 stateful · 2026-09-04 11:56:27 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,894,422
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
0x5acec890
· blocks 2
#5
execOrders
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
cancel
#3
execOrders
· blocks 1
#7
execFwdPositionOpsV2
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a1711ab…1ee8
0x34b655…2a6f
6 touches
3 conflicts
0xe3a4bca8…9120
0x34b655…2a6f
6 touches
3 conflicts
0xe8114298…585b
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x4b1dbc73…1e42
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
3 conflicts on slot
0x3a1711ab90…521ee8
Audit this contract →
← previous block
·
next block →
recent activity