pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,842,775
← previous block
next block →
recent activity
Analyzing
Block #97,842,775
10 transactions · 10 stateful · 2026-08-21 06:54:31 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,842,775
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 3
#4
0xab083028
#6
execFwdPositionOpsV2
#7
setData
#8
0x59558d29
#9
execOrders
#2
execOrders
· blocks 1
#5
execFwdPositionOpsV2
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x03a1f023…e7c5
0x34b655…2a6f
4 touches
1 conflict
0x1153fc25…28f2
0x34b655…2a6f
2 touches
0 conflicts
0x200675c3…4163
0x34b655…2a6f
2 touches
0 conflicts
0x2328941c…84d3
0x34b655…2a6f
2 touches
0 conflicts
0x41be9e75…9773
0x34b655…2a6f
2 touches
0 conflicts
0x51f83dc2…7bc2
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
3 conflicts on slot
0x7de579746e…f0f5ba
Audit this contract →
← previous block
·
next block →
recent activity