pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,186,130
← previous block
next block →
recent activity
Analyzing
Block #106,186,130
9 transactions · 9 stateful · 2026-09-19 13:13:47 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,186,130
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x5acec890
#4
setData
#5
artefact_keep
#6
execFwdPositionOpsV2
· blocks 1
#8
0x6aae8a8e
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x0965547c…bf94
0x34b655…2a6f
2 touches
0 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
2 touches
0 conflicts
0x2631b5d1…886b
0x34b655…2a6f
2 touches
0 conflicts
0x39561c15…c70f
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
0xd41f513688…4197c6
Audit this contract →
← previous block
·
next block →
recent activity