pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,196,766
← previous block
next block →
recent activity
Analyzing
Block #99,196,766
13 transactions · 11 stateful · 2026-08-26 01:23:19 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,196,766
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute_route
#3
0xac6dd8…0aba
#4
0x59558d29
#5
updatePriceFeedsIfNecessary
#6
execFwdPositionOpsV2
#7
0x3f5c179b
· blocks 1
#9
forward
#10
forward
#11
execFwdPositionOpsV2
#12
setData
#8
batchUpdate
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
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x48cf4743…bfe1
0x851145…3f07
4 touches
1 conflict
0x7ea2bdd4…b4b0
0x851145…3f07
4 touches
1 conflict
0x9c3d8416…d9b4
0x851145…3f07
3 touches
1 conflict
0x03622417…0bd7
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69d
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccc
0x2880ab…7b43
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity