pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,302,780
← previous block
next block →
recent activity
Analyzing
Block #101,302,780
11 transactions · 10 stateful · 2026-09-02 10:19:51 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,302,780
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrder
#3
execOrder
#4
0x5acec890
#5
0x5acec890
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0xef048f92…572b
0x34b655…2a6f
4 touches
1 conflict
0xffcbad76…e553
0x34b655…2a6f
3 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x184b9553…ecb2
0x34b655…2a6f
2 touches
0 conflicts
0x2ad2f4bc…1800
0x34b655…2a6f
2 touches
0 conflicts
0x3a1c994d…0ea2
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
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
0x290abc804f…baf605
Audit this contract →
← previous block
·
next block →
recent activity