pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,577,713
← previous block
next block →
recent activity
Analyzing
Block #89,577,713
9 transactions · 9 stateful · 2026-07-23 05:47:19 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,577,713
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#8
0xc7e3ec2c
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e19c9a0…7d86
0x34b655…2a6f
4 touches
1 conflict
0xa85efb73…a0c1
0x34b655…2a6f
4 touches
1 conflict
0xacaba0ad…e266
0x34b655…2a6f
4 touches
1 conflict
0xdaf5ed0d…16ae
0x34b655…2a6f
4 touches
1 conflict
0xdaf5ed0d…16af
0x34b655…2a6f
4 touches
1 conflict
0xe3f2706b…d3ec
0x34b655…2a6f
4 touches
1 conflict
0xe73ab2bc…7cd9
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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
0x6e19c9a020…2f7d86
Audit this contract →
← previous block
·
next block →
recent activity