pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,699,799
← previous block
next block →
recent activity
Analyzing
Block #90,699,799
9 transactions · 7 stateful · 2026-07-27 06:26:41 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,699,799
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xb264ae19
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
0x3f5c179b
#7
execFwdPositionOps
· blocks 1
#3
0xb264ae19
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2f948bb…8304
0x34b655…2a6f
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x322266fd…529d
0x754704…b603
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0xb07a35ae…9f83
0x754704…b603
4 touches
1 conflict
0xdd451ba4…df49
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 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
1 conflict on slot
0xc2f948bb7c…be8304
Audit this contract →
← previous block
·
next block →
recent activity