pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,020,135
← previous block
next block →
recent activity
Analyzing
Block #99,020,135
12 transactions · 12 stateful · 2026-08-25 10:29:45 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,020,135
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0x5acec890
· blocks 1
#4
0x59558d29
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
0x94defb17
· blocks 1
#10
setData
#11
execOrders
#5
execFwdPositionOpsV2
#9
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60098871…653a
0x8964d7…10f8
4 touches
1 conflict
0x60098871…653b
0x8964d7…10f8
4 touches
1 conflict
0x60098871…653e
0x8964d7…10f8
4 touches
1 conflict
0x60098871…653f
0x8964d7…10f8
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x60098871d6…5e653a
Audit this contract →
← previous block
·
next block →
recent activity