pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,041,202
← previous block
next block →
recent activity
Analyzing
Block #91,041,202
12 transactions · 10 stateful · 2026-07-28 11:05:09 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,041,202
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
· blocks 1
#2
updatePrices
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
transfer
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
#5
0x0f6795d9
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
9
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57b02276…db3f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x35ec2b20…6174
0x34b655…2a6f
4 touches
1 conflict
0x62015faa…f8f0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59b0a8da…0928
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
0x57b02276ff…84db3f
Audit this contract →
← previous block
·
next block →
recent activity