pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,984,401
← previous block
next block →
recent activity
Analyzing
Block #98,984,401
12 transactions · 12 stateful · 2026-08-25 07:28:09 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,984,401
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
matchOrders
· blocks 1
#4
execOrders
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
0x29eed2d3
#10
execFwdPositionOpsV2
#11
setData
#3
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53e67340…60f7
0x754704…b603
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0xf00d2133…d68e
0x754704…b603
4 touches
1 conflict
0x48961b46…3dad
0x99c7a7…8bf0
4 touches
1 conflict
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x2191259f…1ac9
0x2a68ba…90c5
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:
USDC (USDC)
1 conflict on slot
0x53e6734022…4a60f7
Audit this contract →
← previous block
·
next block →
recent activity