pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,636,934
← previous block
next block →
recent activity
Analyzing
Block #105,636,934
16 transactions · 15 stateful · 2026-09-17 15:07:16 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,636,934
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x5acec890
· blocks 1
#3
0xab083028
#4
0xab083028
#6
0x5acec890
#7
artefact_keep
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
handleOps
#11
forward
#12
execFwdPositionOpsV2
#13
setData
#14
execOrders
#15
execOrders
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x1d4ac81b…82da
0x34b655…2a6f
2 touches
0 conflicts
0x3305c6ab…3ddb
0x34b655…2a6f
2 touches
0 conflicts
0x400a96f9…fa17
0x34b655…2a6f
2 touches
0 conflicts
0x49065fe2…5f2d
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity