pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,037,309
← previous block
next block →
recent activity
Analyzing
Block #99,037,309
11 transactions · 11 stateful · 2026-08-25 11:57:22 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,037,309
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#8
bet
#9
0x6a8d839a
#10
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0xcc05f2ef…06fd
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x820d7282…6c34
0x34b655…2a6f
4 touches
1 conflict
0x13b1d959…1c28
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x2d5e3771…9a87
0x34b655…2a6f
2 touches
0 conflicts
0x38dee07f…7598
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
0x62030a8195…5491be
Audit this contract →
← previous block
·
next block →
recent activity