pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,248,341
← previous block
next block →
recent activity
Analyzing
Block #99,248,341
13 transactions · 13 stateful · 2026-08-26 05:42:48 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,248,341
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
execOrders
#4
0x5acec890
#5
0x59558d29
#6
executeBatch
· blocks 1
#8
setData
#9
execFwdPositionOpsV2
#10
0x3f5c179b
#11
execOrders
· blocks 1
#7
executeBatch
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57070322…bc66
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5bab6294…795b
0xe52b14…7230
3 touches
1 conflict
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x2202504e…fad0
0x34b655…2a6f
2 touches
0 conflicts
0x2c97e962…ce1d
0x34b655…2a6f
2 touches
0 conflicts
0x6549c516…d8c9
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:
0xe52b1424…bb7230
1 conflict on slot
0x570703220d…6ebc66
Audit this contract →
← previous block
·
next block →
recent activity