pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,977,624
← previous block
next block →
recent activity
Analyzing
Block #94,977,624
8 transactions · 7 stateful · 2026-08-11 05:26:25 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,977,624
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
· blocks 3
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
setData
#2
placeAndExecuteMarketBuy
· blocks 2
#3
placeAndExecuteMarketBuy
· blocks 1
#4
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x0402a9d1…2de9
0x065c9d…c394
6 touches
3 conflicts
0x7e0b7922…c351
0x754704…b603
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x0c612d13…2829
0x34b655…2a6f
2 touches
0 conflicts
0x0e8036e7…b70a
0x34b655…2a6f
2 touches
0 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
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
6 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity