pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,760,188
← previous block
next block →
recent activity
Analyzing
Block #105,760,188
12 transactions · 11 stateful · 2026-09-18 01:27:37 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,760,188
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x5acec890
· blocks 2
#4
execPerpOps
#5
execPerpOps
#6
setData
#7
updatePosition
#8
0xed82b078
#9
0x6aac938c
#10
execOrders
· blocks 1
#3
0x928e4afa
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0613d380…8325
0x34b655…2a6f
2 touches
0 conflicts
0x0c6a407c…2b73
0x34b655…2a6f
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x167cf78a…79e3
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity