pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,431,757
← previous block
next block →
recent activity
Analyzing
Block #90,431,757
9 transactions · 9 stateful · 2026-07-26 07:57:04 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,431,757
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x0c7abd22
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
0x6a65be48
#7
0xe9316489
#8
setData
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43121a72…4b1c
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x96c6ca66…371b
0x34b655…2a6f
4 touches
1 conflict
0xb8746edd…bc38
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x220122d0…40f6
0x34b655…2a6f
2 touches
0 conflicts
0x27034002…2f27
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
0x43121a72a3…9d4b1c
Audit this contract →
← previous block
·
next block →
recent activity