pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,208,412
← previous block
next block →
recent activity
Analyzing
Block #102,208,412
14 transactions · 14 stateful · 2026-09-05 14:28:21 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,208,412
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
· blocks 1
#4
0xab083028
#5
0xab083028
#6
0xab083028
#7
0x5acec890
#8
0x5acec890
#9
0x5acec890
#10
0x59558d29
#11
execFwdPositionOpsV2
#12
setData
#13
0x57368ddf
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae8a7697…9685
0x34b655…2a6f
4 touches
1 conflict
0xdec2aeb2…0586
0x34b655…2a6f
4 touches
1 conflict
0xeb4304a5…dd06
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x1f33cfff…f004
0x34b655…2a6f
4 touches
1 conflict
0x25fd5528…ff50
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x65e5d090…b689
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
1 conflict on slot
0xae8a76973a…5c9685
Audit this contract →
← previous block
·
next block →
recent activity