pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,812,228
← previous block
next block →
recent activity
Analyzing
Block #99,812,228
11 transactions · 9 stateful · 2026-08-28 05:13:25 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,812,228
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0xab083028
#5
0x5acec890
#6
execPerpOps
#7
execOrders
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0x777c9106…162a
0x754704…b603
4 touches
1 conflict
0x079bf666…56c4
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x68c08dd231…8fbe14
Audit this contract →
← previous block
·
next block →
recent activity