pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,287,871
← previous block
next block →
recent activity
Analyzing
Block #99,287,871
12 transactions · 10 stateful · 2026-08-26 09:01:44 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,287,871
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x440755…8d97
#2
0x3f0cf8…472e
#3
execOrders
#4
executeBatch
#5
execFwdPositionOpsV2
· blocks 1
#6
forward
#7
forward
#9
0x6a8eabf0
#10
setData
#11
execOrders
#8
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9c561a3…46b4
0x34b655…2a6f
4 touches
1 conflict
0x5984f63c…7fca
0x34b655…2a6f
4 touches
1 conflict
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x461661b9…f714
0x34b655…2a6f
2 touches
0 conflicts
0x4b52d0b9…2b40
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
0x34b655…2a6f
2 touches
0 conflicts
0x8c60ff10…5df7
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
0xb9c561a3fe…8b46b4
Audit this contract →
← previous block
·
next block →
recent activity