pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,815,975
← previous block
next block →
recent activity
Analyzing
Block #101,815,975
11 transactions · 9 stateful · 2026-09-04 05:21:40 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,815,975
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
0x5acec890
#4
0x3e2e8792
#5
0x59558d29
#6
forward
#7
execFwdPositionOpsV2
#8
forward
#9
execFwdPositionOpsV2
#10
setData
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaea4b94…0aea
0x34b655…2a6f
4 touches
1 conflict
0x3cb45e6c…97c0
0x34b655…2a6f
4 touches
1 conflict
0x7032a740…2878
0x34b655…2a6f
4 touches
1 conflict
0xc3e8eb72…7ab5
0x34b655…2a6f
4 touches
1 conflict
0x2ba56d60…09dc
0x34b655…2a6f
2 touches
0 conflicts
0xc6b75e8a…fae8
0x34b655…2a6f
2 touches
0 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
0x4893968b…28d0
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
0xfaea4b9439…210aea
Audit this contract →
← previous block
·
next block →
recent activity