pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,803,582
← previous block
next block →
recent activity
Analyzing
Block #90,803,582
11 transactions · 11 stateful · 2026-07-27 15:08:49 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,803,582
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x5a5d9a99
#4
0x785f5745
#5
0x0f6795d9
· blocks 1
#6
collect
#8
updateDataFeedsValuesPartial
#9
0x6a6774f8
#10
setData
#2
updatePrices
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1144e3…ca4e
0x34b655…2a6f
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x8546c118…9f9d
0x0c65a0…0852
2 touches
0 conflicts
0x0494220d…abf6
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
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
0x5e1144e3b4…34ca4e
Audit this contract →
← previous block
·
next block →
recent activity