pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,802,097
← previous block
next block →
recent activity
Analyzing
Block #101,802,097
9 transactions · 9 stateful · 2026-09-04 04:11:52 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,802,097
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x59558d29
#4
setData
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
execOrders
· blocks 1
#2
execOrders
#8
execOrders
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
0x3cb45e6c…97c0
0x34b655…2a6f
4 touches
1 conflict
0x3a8a3357…834e
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x54363dda…bf0c
0x34b655…2a6f
4 touches
1 conflict
0xc7d734c2…b3f8
0x34b655…2a6f
4 touches
1 conflict
0xca70fa2c…6a7e
0x34b655…2a6f
4 touches
1 conflict
0xd688757b…292b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
0x3cb45e6c72…e497c0
Audit this contract →
← previous block
·
next block →
recent activity