pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,991,485
← previous block
next block →
recent activity
Analyzing
Block #101,991,485
9 transactions · 9 stateful · 2026-09-04 20:08:48 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,991,485
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrders
· blocks 1
#4
execOrders
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
0x6a9b25c8
#8
setData
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6875750…9542
0x34b655…2a6f
4 touches
1 conflict
0xee46716c…d788
0x34b655…2a6f
4 touches
1 conflict
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x5eca016a…65e6
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
0x34b655…2a6f
4 touches
1 conflict
0x7daf6443…fd36
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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
0xe6875750e1…ed9542
Audit this contract →
← previous block
·
next block →
recent activity