pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,938,202
← previous block
next block →
recent activity
Analyzing
Block #101,938,202
11 transactions · 10 stateful · 2026-09-04 15:38:32 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,938,202
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5acec890
#3
0x59558d29
#4
setApprovalForAll
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#8
0x6a9ae670
#9
execOrders
#7
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x3bd7558f…4af6
0x34b655…2a6f
4 touches
1 conflict
0x71b395d9…1697
0x34b655…2a6f
4 touches
1 conflict
0x81f691b8…0f1a
0x34b655…2a6f
4 touches
1 conflict
0xaf199a64…16ed
0x34b655…2a6f
4 touches
1 conflict
0x0c9efe65…2a73
0x34b655…2a6f
2 touches
0 conflicts
0x10a94122…c9c6
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
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
0x51fc8795c8…57126f
Audit this contract →
← previous block
·
next block →
recent activity