pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,318,164
← previous block
next block →
recent activity
Analyzing
Block #94,318,164
9 transactions · 7 stateful · 2026-08-08 21:59:56 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,318,164
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39435dac
#2
0x5acec890
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
placeAndExecuteMarketBuy
· blocks 2
#8
setData
#6
placeAndExecuteMarketBuy
· blocks 1
#7
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xae80a8b2…c8da
0xa6afd3…d132
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x38855b14…b4ec
0x34b655…2a6f
2 touches
0 conflicts
0x3bba6aa0…e367
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
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
3 conflicts on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity