pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,252,169
← previous block
next block →
recent activity
Analyzing
Block #99,252,169
10 transactions · 10 stateful · 2026-08-26 06:02:03 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
#99,252,169
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 1
#4
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#6
0x3f5c179b
#7
0xd708c5d8
#8
setData
#3
0x5acec890
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd2dfd9bc…3eec
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x12e77486…ec2b
0x34b655…2a6f
2 touches
0 conflicts
0x1ada3764…d906
0x34b655…2a6f
2 touches
0 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
2 touches
0 conflicts
0x4b5f2081…f3c5
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
1 conflict on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity