pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,916,187
← previous block
next block →
recent activity
Analyzing
Block #90,916,187
11 transactions · 10 stateful · 2026-07-28 00:35:25 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,916,187
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a67f9c5
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 2
#7
0x3f5c179b
#8
forward
#9
setData
#6
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0c376bba…95b1
0x34b655…2a6f
2 touches
0 conflicts
0x0ffb3a5c…e790
0x34b655…2a6f
2 touches
0 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x18316bb4…d507
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
0xebac0f82ec…86a49c
Audit this contract →
← previous block
·
next block →
recent activity