pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,243,661
← previous block
next block →
recent activity
Analyzing
Block #99,243,661
16 transactions · 15 stateful · 2026-08-26 05:19:15 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,243,661
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x6a8e77cb
#2
0x8263f5d9
#3
0x928e4afa
#4
execOrders
#5
execFwdPositionOpsV2
#6
proposeResolution
#7
0x6a8e77cb
#8
setData
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1cfa777f…cb6c
0x34b655…2a6f
2 touches
0 conflicts
0x1f8db170…5439
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x554873fd…2ff4
0x34b655…2a6f
2 touches
0 conflicts
0x60a6d552…3d3a
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.
← previous block
·
next block →
recent activity