pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,398,511
← previous block
next block →
recent activity
Analyzing
Block #102,398,511
8 transactions · 7 stateful · 2026-09-06 06:31:27 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,398,511
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#5
setData
#7
execOrders
#2
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c67d31e…3dbe
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x1d40cce0…8db9
0x34b655…2a6f
2 touches
0 conflicts
0x1e4cc8a7…0519
0x34b655…2a6f
2 touches
0 conflicts
0x25cb70ed…5ead
0x34b655…2a6f
2 touches
0 conflicts
0x290abc80…f605
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
0x3c67d31e03…f03dbe
Audit this contract →
← previous block
·
next block →
recent activity