pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,779,274
← previous block
next block →
recent activity
Analyzing
Block #99,779,274
8 transactions · 8 stateful · 2026-08-28 02:26:21 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,779,274
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrder
#4
execOrder
· blocks 1
#6
bet
#7
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x3d538e8e…702c
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x0d378dc8…5e93
0x34b655…2a6f
2 touches
0 conflicts
0x51af0e92…4020
0x34b655…2a6f
2 touches
0 conflicts
0x70d81211…f49f
0x34b655…2a6f
2 touches
0 conflicts
0x73e48148…c60c
0x34b655…2a6f
2 touches
0 conflicts
0x81501297…c4b7
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
0x3a7fb5b5df…c1f0e5
Audit this contract →
← previous block
·
next block →
recent activity