pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,206,245
← previous block
next block →
recent activity
Analyzing
Block #104,206,245
10 transactions · 7 stateful · 2026-09-12 14:43:17 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,206,245
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
0x59558d29
#4
0x59558d29
#5
execOrders
· blocks 1
#6
setData
#8
0x6aa56508
#9
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x1398e9f0…69ac
0x34b655…2a6f
4 touches
1 conflict
0x06c469dd…fdfe
0x34b655…2a6f
2 touches
0 conflicts
0x100812e9…12b7
0x34b655…2a6f
2 touches
0 conflicts
0x3270d9f8…099a
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x818e1296…f4d7
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
0xc7954a6095…b3d294
Audit this contract →
← previous block
·
next block →
recent activity