pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,395,318
← previous block
next block →
recent activity
Analyzing
Block #90,395,318
10 transactions · 8 stateful · 2026-07-26 04:49:45 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,395,318
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
0x0f6795d9
· blocks 1
#6
0x39435dac
#7
0x6a659261
#8
setData
#9
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x74dae4f2…f2d8
0x34b655…2a6f
2 touches
0 conflicts
0x9c166a56…0356
0x34b655…2a6f
2 touches
0 conflicts
0xc573ca73…fcd2
0x34b655…2a6f
2 touches
0 conflicts
0xfcaee83d…428d
0x34b655…2a6f
2 touches
0 conflicts
0x1716b13d…99cc
0xc8689a…ee79
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity