pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,744,099
← previous block
next block →
recent activity
Analyzing
Block #98,744,099
11 transactions · 8 stateful · 2026-08-24 11:18:51 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,744,099
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
execOrders
#4
0x59558d29
#5
execOrder
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0x018a47fe…0ad4
0x34b655…2a6f
2 touches
0 conflicts
0x059d1c22…d4f3
0x34b655…2a6f
2 touches
0 conflicts
0x0a225025…7f41
0x34b655…2a6f
2 touches
0 conflicts
0x1e9fccc4…5c21
0x34b655…2a6f
2 touches
0 conflicts
0x24bb46f7…3853
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
0x414698942a…665990
Audit this contract →
← previous block
·
next block →
recent activity