pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,828,697
← previous block
next block →
recent activity
Analyzing
Block #89,828,697
10 transactions · 9 stateful · 2026-07-24 05:03:54 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,828,697
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
executeBatch
#3
0x0f6795d9
#4
0xc925b3a5
#5
0x39435dac
· blocks 3
#7
setData
#6
0x39435dac
· blocks 2
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4dc1328…d42d
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x89cbeab8…afdf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x58733c38…f2cd
0xe52b14…7230
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
3 conflicts on slot
0xa4dc1328e9…dbd42d
Audit this contract →
← previous block
·
next block →
recent activity