pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,468,582
← previous block
next block →
recent activity
Analyzing
Block #102,468,582
8 transactions · 8 stateful · 2026-09-06 12:26:25 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,468,582
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x0c7abd22
#4
updatePrices
#5
0xab083028
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd7574f…a3a2
0x34b655…2a6f
4 touches
1 conflict
0xd98afa6e…3364
0x34b655…2a6f
4 touches
1 conflict
0xe0da07e4…ccf2
0x34b655…2a6f
4 touches
1 conflict
0xf4e1756d…1f63
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x6dc1811e…2588
0x34b655…2a6f
4 touches
1 conflict
0x73ae20cb…19f1
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
0xfcd7574f97…54a3a2
Audit this contract →
← previous block
·
next block →
recent activity