pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,242,837
← previous block
next block →
recent activity
Analyzing
Block #99,242,837
11 transactions · 10 stateful · 2026-08-26 05:15:06 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,242,837
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x8f9ad8be
#3
setData
#4
execFwdPositionOpsV2
· blocks 2
#6
claim
· blocks 1
#8
updateTemporalNumericValuesV1
#9
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#7
0xc925b3a5
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x09941bac…479b
0x8964d7…10f8
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
3 touches
1 conflict
0x09941bac…479c
0x8964d7…10f8
3 touches
1 conflict
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity