pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,774,322
← previous block
next block →
recent activity
Analyzing
Block #90,774,322
10 transactions · 10 stateful · 2026-07-27 12:41:34 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,774,322
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
· blocks 1
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
0x3f5c179b
#7
0x6a675276
#8
setData
#4
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x623fd48c…9d77
0x34b655…2a6f
4 touches
1 conflict
0x768d379f…f440
0x34b655…2a6f
4 touches
1 conflict
0x084666b0…0702
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0e3b59e9…d9d0
0x34b655…2a6f
4 touches
1 conflict
0xb8806526…e31f
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
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
0x623fd48ce3…769d77
Audit this contract →
← previous block
·
next block →
recent activity