pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,840,154
← previous block
next block →
recent activity
Analyzing
Block #90,840,154
6 transactions · 6 stateful · 2026-07-27 18:12:53 UTC
Parallelism
67
/100
Blocked
50
%
Avg conflicts / tx
0.5
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,840,154
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 3
#4
setData
#2
execFwdPositionOps
#3
execFwdPositionOps
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x663ab2c3…67ab
0x34b655…2a6f
4 touches
1 conflict
0xc3fc40da…1c60
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83f9
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
0xffb2bfcf79…31b92a
Audit this contract →
← previous block
·
next block →
recent activity