pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,039,445
← previous block
next block →
recent activity
Analyzing
Block #102,039,445
11 transactions · 9 stateful · 2026-09-05 00:11:44 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,039,445
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
createModule
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
execOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xf8f2714d…b34c
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
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
0x261cbea79d…12e35e
Audit this contract →
← previous block
·
next block →
recent activity