pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,543,236
← previous block
next block →
recent activity
Analyzing
Block #90,543,236
11 transactions · 11 stateful · 2026-07-26 17:19:04 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,543,236
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
transfer
#8
setData
#9
0xc7e3ec2c
#10
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a57c929…b1d4
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
0x34b655…2a6f
2 touches
0 conflicts
0x78860c4f…cade
0x34b655…2a6f
2 touches
0 conflicts
0xeefeaede…42c7
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
0x8a57c92941…33b1d4
Audit this contract →
← previous block
·
next block →
recent activity