pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,683,230
← previous block
next block →
recent activity
Analyzing
Block #105,683,230
11 transactions · 9 stateful · 2026-09-17 19:00:19 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
#105,683,230
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x0c7abd22
#3
0x59558d29
#4
borrow
#5
0x0c7abd22
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#9
forward
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23d67fe1…2ebf
0x000000…012a
2 touches
0 conflicts
0x236891fe…7521
0x57ea24…2cec
2 touches
0 conflicts
0xa7292de5…3aa3
0x57ea24…2cec
2 touches
0 conflicts
0xe9e70c2e…8e50
0x690ad2…09d3
2 touches
0 conflicts
0xe9e70c2e…8e51
0x690ad2…09d3
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity