pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,406,302
← previous block
next block →
recent activity
Analyzing
Block #93,406,302
12 transactions · 11 stateful · 2026-08-05 17:26:32 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,406,302
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x6a7372c0
#3
updatePrices
#4
execFwdPositionOps
#5
0x3f5c179b
#7
execFwdPositionOps
· blocks 1
#9
setData
#10
execOrders
#11
0x59558d29
#6
0x3f5c179b
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x529e53cf…38e4
0xa6afd3…d132
4 touches
1 conflict
0x989252a1…d812
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x76c21609…ca65
0xa6afd3…d132
3 touches
1 conflict
0x127a12d4…3119
0xa6afd3…d132
3 touches
1 conflict
0xaec95739…619e
0xa6afd3…d132
3 touches
1 conflict
0x581039cf…7d83
0xa6afd3…d132
3 touches
1 conflict
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity