pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,291,868
← previous block
next block →
recent activity
Analyzing
Block #90,291,868
11 transactions · 10 stateful · 2026-07-25 20:00:57 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,291,868
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 3
#4
execFwdPositionOps
#6
execOrders
#8
execFwdPositionOps
#9
setData
#5
execOrders
· blocks 2
#7
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x47a10383…3e35
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x7ba216b2…eec1
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
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
0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block
·
next block →
recent activity