pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,952,601
← previous block
next block →
recent activity
Analyzing
Block #94,952,601
8 transactions · 7 stateful · 2026-08-11 03:20:35 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,952,601
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#2
0xa96df62f
#3
placeAndExecuteMarketBuy
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketBuy
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0xa8e98b9f…5935
0x01bff4…1071
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity