pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,844,342
← previous block
next block →
recent activity
Analyzing
Block #89,844,342
11 transactions · 8 stateful · 2026-07-24 06:22:53 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,844,342
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xba2e28…3831
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
forward
#5
0x0f6795d9
· blocks 1
#6
0x39435dac
#7
0x39435dac
· blocks 1
#8
setData
#10
0x39435dac
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x434010de…83fe
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xfad0b123…bf91
0x34b655…2a6f
4 touches
1 conflict
0x12194add…8a48
0x34b655…2a6f
2 touches
0 conflicts
0x12194add…8a49
0x34b655…2a6f
2 touches
0 conflicts
0x141cd942…56ac
0x34b655…2a6f
2 touches
0 conflicts
0x2145086e…39c6
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity