pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,995,115
← previous block
next block →
recent activity
Analyzing
Block #90,995,115
10 transactions · 10 stateful · 2026-07-28 07:12:40 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,995,115
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execOrder
· blocks 2
#3
updatePrices
#4
0x5a5d9a99
· blocks 1
#7
updateTemporalNumericValuesV1
#8
0x6a6856df
#9
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eb38592…1803
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x623fd48c…9d77
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
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
0x9eb38592b3…871803
Audit this contract →
← previous block
·
next block →
recent activity