pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,186,064
← previous block
next block →
recent activity
Analyzing
Block #99,186,064
9 transactions · 8 stateful · 2026-08-26 00:29:27 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,186,064
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x80419567
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
execOrders
· blocks 1
#7
resolve
#8
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xf0b9b3ee…c064
0x000000…012a
2 touches
0 conflicts
0x6059a384…dcdf
0x699abc…6a3b
2 touches
0 conflicts
0x7d3ca10a…7c07
0x699abc…6a3b
2 touches
0 conflicts
0x8a98d12c…5a78
0x754704…b603
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
0x6f132c01d5…7dcdcc
Audit this contract →
← previous block
·
next block →
recent activity