pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,968,738
← previous block
next block →
recent activity
Analyzing
Block #101,968,738
12 transactions · 10 stateful · 2026-09-04 18:13:22 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,968,738
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execOrders
#3
0x59558d29
#4
0x000000b2
#6
0x57368ddf
#7
execFwdPositionOpsV2
#8
revealPack
#9
setData
#10
0x000000b2
#11
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b13e91…855d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x014e90b3…470f
0x34b655…2a6f
2 touches
0 conflicts
0x101be604…5db0
0x34b655…2a6f
2 touches
0 conflicts
0x1f4e6c86…7789
0x34b655…2a6f
2 touches
0 conflicts
0x2a565afa…37fc
0x34b655…2a6f
2 touches
0 conflicts
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x39ccd26a…4654
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
0x91b13e914b…cb855d
Audit this contract →
← previous block
·
next block →
recent activity