pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,499,780
← previous block
next block →
recent activity
Analyzing
Block #93,499,780
13 transactions · 12 stateful · 2026-08-06 01:16:29 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,499,780
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
matchOrders
· blocks 1
#5
0x39435dac
#6
0x5acec890
#7
0x0f6795d9
#8
0x0f6795d9
#9
forward
#10
0x6a73e0e4
#11
setData
#12
0x59558d29
#4
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ba2c03b…3d9f
0x754704…b603
4 touches
1 conflict
0x9b2b4ba7…f42d
0x754704…b603
4 touches
1 conflict
0xc07e7b41…7f0a
0x754704…b603
4 touches
1 conflict
0xdf1473d0…5fea
0x99c7a7…8bf0
4 touches
1 conflict
0xf7cce5b0…5c16
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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
0x0ba2c03be9…e03d9f
Audit this contract →
← previous block
·
next block →
recent activity