pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,293,600
← previous block
next block →
recent activity
Analyzing
Block #90,293,600
11 transactions · 11 stateful · 2026-07-25 20:09:45 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,293,600
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
0x3f5c179b
#5
execFwdPositionOps
#6
execOrders
#7
0x6a651880
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe27c3b63…76a8
0x34b655…2a6f
4 touches
1 conflict
0x6eb8ea2b…db01
0x34b655…2a6f
4 touches
1 conflict
0x808415c0…7f83
0x34b655…2a6f
4 touches
1 conflict
0x81538adb…d63a
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0xbc2d4ffa…3942
0x34b655…2a6f
4 touches
1 conflict
0xc44901fe…0fef
0x34b655…2a6f
4 touches
1 conflict
0xc8b71688…1d40
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
0xe27c3b636f…db76a8
Audit this contract →
← previous block
·
next block →
recent activity