pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,567,757
← previous block
next block →
recent activity
Analyzing
Block #89,567,757
9 transactions · 7 stateful · 2026-07-23 04:40:48 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
#89,567,757
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
executeBatch
#3
0x0f6795d9
#4
0x6a619bc8
#5
setData
#6
exactInputSingle
#7
0x39435dac
· blocks 1
#8
0x39435dac
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
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0413d1ed…ad55
0x34b655…2a6f
2 touches
0 conflicts
0x4b64ba3d…113f
0x34b655…2a6f
2 touches
0 conflicts
0xa47b7766…ee6e
0x34b655…2a6f
2 touches
0 conflicts
0xaa476cfe…7064
0x34b655…2a6f
2 touches
0 conflicts
0xbcbf5d09…8bac
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
0xffc2f21efe…ecb393
Audit this contract →
← previous block
·
next block →
recent activity