pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,946,725
← previous block
next block →
recent activity
Analyzing
Block #90,946,725
11 transactions · 10 stateful · 2026-07-28 03:09:01 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,946,725
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6c05cd2b
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
executeBatch
· blocks 1
#8
0x6a681dc4
#9
setData
#10
updatePriceFeeds
#5
0x0f6795d9
#7
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x4565f421…80b9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd7668c61…55f8
0x34b655…2a6f
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0x66d2b56f…4376
0xe52b14…7230
3 touches
1 conflict
0xff8b218b…8be7
0x40c49f…2af0
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity