pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,483,186
← previous block
next block →
recent activity
Analyzing
Block #90,483,186
9 transactions · 9 stateful · 2026-07-26 12:17:02 UTC
Parallelism
56
/100
Blocked
33
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,483,186
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 3
#7
setData
#8
execOrders
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
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
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xcb499429…3731
0x34b655…2a6f
4 touches
1 conflict
0xed7c8da9…78ce
0x34b655…2a6f
4 touches
1 conflict
0xf961da8b…9367
0x34b655…2a6f
4 touches
1 conflict
0x2132931c…59f7
0x34b655…2a6f
4 touches
1 conflict
0x2132931c…59f8
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity