pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,959,020
← previous block
next block →
recent activity
Analyzing
Block #106,959,020
15 transactions · 14 stateful · 2026-09-22 06:04:49 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,959,020
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xefdb8189
#3
0xab083028
#4
0xab083028
#5
0x59558d29
#6
execPerpOps
#7
setData
#8
execFwdPositionOpsV2
#9
executeBatch
· blocks 1
#11
execOrders
#12
0x6ab21a84
#13
execOrders
#14
execOrders
#10
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x2ac50403…d307
0xe52b14…7230
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x697200a9…f0f2
0x34b655…2a6f
2 touches
0 conflicts
0x6c28863e…840e
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity