pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,290,993
← previous block
next block →
recent activity
Analyzing
Block #93,290,993
12 transactions · 11 stateful · 2026-08-05 07:46:47 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,290,993
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updatePrices
#3
multicall
#4
updatePosition
#5
0x3f5c179b
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a72eadf
· blocks 1
#11
0x59558d29
#10
0x6a72eadf
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x06fc25…2f51
2 touches
0 conflicts
0x23b7aa1d…7763
0x06fc25…2f51
2 touches
0 conflicts
0x543d36c3…efd2
0x06fc25…2f51
2 touches
0 conflicts
0x75b5a53d…631d
0x06fc25…2f51
2 touches
0 conflicts
0x889d5e90…929a
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity