pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,693,550
← previous block
next block →
recent activity
Analyzing
Block #89,693,550
11 transactions · 9 stateful · 2026-07-23 17:41:46 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,693,550
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#4
0x62be7533
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
· blocks 1
#10
0xc7e3ec2c
#6
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb573e7c…6830
0x34b655…2a6f
4 touches
1 conflict
0x4ac2a863…cba1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd6ccd20…c33e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6f845aff…9fc9
0x3bd359…433a
2 touches
0 conflicts
0xc6101b5d…4361
0x3bd359…433a
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
0xeb573e7ccc…5d6830
Audit this contract →
← previous block
·
next block →
recent activity