pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,288,219
← previous block
next block →
recent activity
Analyzing
Block #92,288,219
9 transactions · 9 stateful · 2026-08-01 19:40:29 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.56
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,288,219
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 3
#3
execFwdPositionOps
· blocks 2
#6
0x6a6e4c25
#7
setData
#8
execOrders
#2
0x5acec890
#4
execFwdPositionOps
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa435dee8…f2be
0x34b655…2a6f
4 touches
1 conflict
0xabba7bd6…8269
0x34b655…2a6f
4 touches
1 conflict
0xabba7bd6…826a
0x34b655…2a6f
4 touches
1 conflict
0xafb2524a…0ce4
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd1448207…452d
0x34b655…2a6f
4 touches
1 conflict
0x8dd2ae5f…b8dd
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
0xa435dee840…eef2be
Audit this contract →
← previous block
·
next block →
recent activity