pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,745,036
← previous block
next block →
recent activity
Analyzing
Block #99,745,036
11 transactions · 9 stateful · 2026-08-27 23:32:34 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,745,036
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xa96df62f
#3
0xab083028
#4
execOrders
· blocks 1
#5
0x5acec890
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
0xb8024e50
#7
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ffbcf9…8f98
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x461661b9…f714
0x34b655…2a6f
2 touches
0 conflicts
0x78e7f7af…0e0f
0x34b655…2a6f
2 touches
0 conflicts
0x7b6d2deb…dde0
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
0x37ffbcf96b…0e8f98
Audit this contract →
← previous block
·
next block →
recent activity