pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,301,278
← previous block
next block →
recent activity
Analyzing
Block #90,301,278
8 transactions · 7 stateful · 2026-07-25 20:48:48 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,301,278
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
execFwdPositionOps
#5
setData
#6
execOrders
· blocks 1
#4
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14716474…0666
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x04d975c5…0fd7
0x34b655…2a6f
2 touches
0 conflicts
0x061a1fff…507d
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x07ce1f25…cc92
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
0x147164744f…2f0666
Audit this contract →
← previous block
·
next block →
recent activity