pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,977,929
← previous block
next block →
recent activity
Analyzing
Block #100,977,929
10 transactions · 10 stateful · 2026-09-01 07:05:11 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,977,929
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x5acec890
#4
transferWithAuthorization
#5
setData
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
· blocks 1
#9
0x6a96799e
#2
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda50c9d5…674e
0x34b655…2a6f
4 touches
1 conflict
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x70b55eef…7f5c
0x34b655…2a6f
4 touches
1 conflict
0x841b81d2…de5c
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xaaf36ccb…f35c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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
0xda50c9d58b…78674e
Audit this contract →
← previous block
·
next block →
recent activity