pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,797,952
← previous block
next block →
recent activity
Analyzing
Block #101,797,952
11 transactions · 10 stateful · 2026-09-04 03:51:01 UTC
Parallelism
73
/100
Blocked
40
%
Avg conflicts / tx
0.45
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,797,952
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 3
#3
0x0c7abd22
· blocks 1
#5
execOrders
#6
0x59558d29
#8
setData
#9
0x6a9a409d
#2
execOrders
· blocks 1
#4
0x5acec890
#7
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
7
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2222135b…8843
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
4 touches
1 conflict
0xa086cdf1…40e7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
0x6394f64c…95a9
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
3 conflicts on slot
0x2222135b0b…4b8843
Audit this contract →
← previous block
·
next block →
recent activity