pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,950,853
← previous block
next block →
recent activity
Analyzing
Block #94,950,853
11 transactions · 10 stateful · 2026-08-11 03:11:47 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,950,853
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
repayWithCollateral
#5
placeAndExecuteMarketSell
· blocks 1
#6
0x3f5c179b
· blocks 1
#8
0x6a7a936b
#9
setData
#10
0x59558d29
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xeece0d97…0420
0x851145…3f07
3 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x24ca1902…7a87
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0xb64a26cd…4ffa
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
1 conflict on slot
0x07b86c515d…73cdae
Audit this contract →
← previous block
·
next block →
recent activity