pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,501,762
← previous block
next block →
recent activity
Analyzing
Block #101,501,762
9 transactions · 8 stateful · 2026-09-03 03:01:07 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,501,762
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x5acec890
#4
setData
#5
execFwdPositionOpsV2
· blocks 1
#7
forward
#8
0xed82b078
#2
0x0c7abd22
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x28b79b30…1347
0xd32edf…ff58
3 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x09b046db…9f3a
0x34b655…2a6f
2 touches
0 conflicts
0x1f459632…a5d9
0x34b655…2a6f
2 touches
0 conflicts
0x1fcdf998…1e59
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
0x414698942a…66598f
Audit this contract →
← previous block
·
next block →
recent activity