pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,221,984
← previous block
next block →
recent activity
Analyzing
Block #103,221,984
10 transactions · 10 stateful · 2026-09-09 03:48:53 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,221,984
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x5acec890
#4
0x928e4afa
· blocks 1
#5
0x4cb2db39
#6
0x59558d29
#7
setData
#9
0x6aa0d727
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587dcf2c…7759
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xb3ff9ee7…2e3e
0x34b655…2a6f
4 touches
1 conflict
0x58b27dde…52d1
0x34b655…2a6f
4 touches
1 conflict
0x0ade1c5b…d232
0x34b655…2a6f
2 touches
0 conflicts
0x127f7fae…4c21
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x5ee1769f…2d59
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
0x587dcf2cff…267759
Audit this contract →
← previous block
·
next block →
recent activity