pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,457,398
← previous block
next block →
recent activity
Analyzing
Block #90,457,398
11 transactions · 11 stateful · 2026-07-26 10:07:15 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,457,398
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
dagSwapByOrderId
#3
execFwdPositionOps
· blocks 1
#4
setData
#5
0x3f5c179b
#6
0x0c7abd22
#8
execFwdPositionOps
#9
0x6a65dccb
#10
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x997d4606…b060
0x34b655…2a6f
4 touches
1 conflict
0x997d4606…b061
0x34b655…2a6f
4 touches
1 conflict
0xaad63a59…8021
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe16c5b90…fd76
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6c
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6d
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
1 conflict on slot
0xed59b1cd08…c98509
Audit this contract →
← previous block
·
next block →
recent activity