pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,374,691
← previous block
next block →
recent activity
Analyzing
Block #90,374,691
7 transactions · 6 stateful · 2026-07-26 03:03:43 UTC
Parallelism
43
/100
Blocked
50
%
Avg conflicts / tx
0.86
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,374,691
· 7 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execOrders
· blocks 3
#4
execOrders
· blocks 2
#5
execOrders
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89492cdf…3d49
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
6 touches
3 conflicts
0x64e5f38d…187c
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xc434fbdd…f791
0x34b655…2a6f
6 touches
3 conflicts
0x79bdf655…91f2
0x34b655…2a6f
4 touches
1 conflict
0x91f687f3…aca8
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
6 conflicts on slot
0x89492cdf18…5f3d49
Audit this contract →
← previous block
·
next block →
recent activity