pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,490,373
← previous block
next block →
recent activity
Analyzing
Block #101,490,373
9 transactions · 7 stateful · 2026-09-03 02:03:49 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,490,373
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrder
#3
0xab083028
#4
0xab083028
#5
execFwdPositionOpsV2
· blocks 1
#6
buy
#7
0x713f46…b292
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705a9a1a…db08
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0df29722…d3c4
0x34b655…2a6f
2 touches
0 conflicts
0x1513b999…b52e
0x34b655…2a6f
2 touches
0 conflicts
0x21c29152…a782
0x34b655…2a6f
2 touches
0 conflicts
0x25865ac3…144c
0x34b655…2a6f
2 touches
0 conflicts
0x289af619…b3c3
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
0x705a9a1af8…69db08
Audit this contract →
← previous block
·
next block →
recent activity