pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,500,946
← previous block
next block →
recent activity
Analyzing
Block #101,500,946
8 transactions · 7 stateful · 2026-09-03 02:57:01 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,500,946
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0xe3a3c9cc
#3
executeBatch
#5
setData
#6
forward
#7
0x6a98e274
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb70f92cf…da8b
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x1f40a520…152d
0x34b655…2a6f
2 touches
0 conflicts
0x25263e25…1fa7
0x34b655…2a6f
2 touches
0 conflicts
0x270e5664…c0e2
0x34b655…2a6f
2 touches
0 conflicts
0x336486a4…20bd
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
0xb70f92cf9e…55da8b
Audit this contract →
← previous block
·
next block →
recent activity