pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,019,099
← previous block
next block →
recent activity
Analyzing
Block #91,019,099
10 transactions · 10 stateful · 2026-07-28 09:13:56 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,019,099
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#6
0x57368ddf
#8
setData
#9
0xc7e3ec2c
#5
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20492d53…80f9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc4203f4…e206
0x34b655…2a6f
4 touches
1 conflict
0x404215c8…0e49
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6483a537…b63e
0x34b655…2a6f
4 touches
1 conflict
0x675ae01d…750f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
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
3 conflicts on slot
0x20492d531d…7380f9
Audit this contract →
← previous block
·
next block →
recent activity