pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,709,325
← previous block
next block →
recent activity
Analyzing
Block #89,709,325
9 transactions · 7 stateful · 2026-07-23 19:01:16 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,709,325
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executeBatch
#2
forward
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
0x6a626573
#6
execOrders
· blocks 1
#8
execOrders
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x18d19f…aaa2
2 touches
0 conflicts
0x45911da6…5523
0x34b655…2a6f
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x58733c38…f2cd
0xe52b14…7230
2 touches
0 conflicts
0x693b762e…1fcd
0xe52b14…7230
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
0x170e4e4c7c…012b90
Audit this contract →
← previous block
·
next block →
recent activity