pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,557,193
← previous block
next block →
recent activity
Analyzing
Block #93,557,193
9 transactions · 7 stateful · 2026-08-06 06:05:05 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,557,193
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x532c46db
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a742489
#2
0x532c46db
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
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x758f26d7…858f
0x01bff4…1071
2 touches
0 conflicts
0xa8e98b9f…5935
0x01bff4…1071
2 touches
0 conflicts
0xcccd49f7…c87f
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
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
0xa2478c8415…006956
Audit this contract →
← previous block
·
next block →
recent activity