pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,710,229
← previous block
next block →
recent activity
Analyzing
Block #89,710,229
11 transactions · 10 stateful · 2026-07-23 19:05:48 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,710,229
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x3f5c179b
#6
executeBatch
#8
0x39435dac
#9
setData
#10
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0629cebb…4e45
0x34b655…2a6f
4 touches
1 conflict
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x060b4e83…4f56
0x34b655…2a6f
2 touches
0 conflicts
0x09a569d8…2e76
0x34b655…2a6f
2 touches
0 conflicts
0x16545605…c807
0x34b655…2a6f
2 touches
0 conflicts
0x17fff7d7…7b99
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
0x0629cebb8e…b84e45
Audit this contract →
← previous block
·
next block →
recent activity