pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,855,142
← previous block
next block →
recent activity
Analyzing
Block #101,855,142
11 transactions · 11 stateful · 2026-09-04 08:38:42 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,855,142
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x325dd70c
#2
0x6a9a8409
#3
execOrders
#4
0x3e2e8792
· blocks 1
#6
execFwdPositionOpsV2
· blocks 1
#8
executeBatch
#9
setData
#10
execOrders
#5
0x5acec890
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x99449f41…9d5d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd228e29a…a108
0x34b655…2a6f
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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
0x735a86cd19…53b64d
Audit this contract →
← previous block
·
next block →
recent activity