pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,087,713
← previous block
next block →
recent activity
Analyzing
Block #91,087,713
9 transactions · 7 stateful · 2026-07-28 14:59:12 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,087,713
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xd708c5d8
#5
setData
#6
0x61633731
#7
exactInputSingle
#8
0x39435dac
#2
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x079bf666…56c4
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x0b65d0ba…a344
0x34b655…2a6f
2 touches
0 conflicts
0x0b65d0ba…a345
0x34b655…2a6f
2 touches
0 conflicts
0x15437606…7ec7
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity