pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,463,553
← previous block
next block →
recent activity
Analyzing
Block #93,463,553
11 transactions · 11 stateful · 2026-08-05 22:14:22 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,463,553
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
0x5acec890
#5
0x0f6795d9
#6
redeemDelegations
#7
0x5339c59f
#8
0x0f6795d9
#9
setData
#10
0x59558d29
#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
0xcf3f3349…b858
0x754704…b603
4 touches
1 conflict
0xe96cbc90…be66
0x754704…b603
4 touches
1 conflict
0x0d528651…72f0
0x754704…b603
4 touches
1 conflict
0x42b1e4f4…ee71
0x99c7a7…8bf0
4 touches
1 conflict
0x63d6949a…24cf
0x99c7a7…8bf0
4 touches
1 conflict
0x202ded7c…aca4
0x34b655…2a6f
2 touches
0 conflicts
0x2d541549…9cce
0x34b655…2a6f
2 touches
0 conflicts
0x4a558404…51f2
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:
USDC (USDC)
1 conflict on slot
0xcf3f3349c2…96b858
Audit this contract →
← previous block
·
next block →
recent activity