pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,271,795
← previous block
next block →
recent activity
Analyzing
Block #75,271,795
9 transactions · 8 stateful · 2026-05-17 22:23:18 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,271,795
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#2
0x0c7abd22
#3
execute302
#6
updateDataFeedsValuesPartial
#7
updateTemporalNumericValuesV1
#8
setData
#4
0xed82b078
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x438cf5f6…f077
0x2a68ba…90c5
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x1570dc2f…2b42
0x065c9d…c394
3 touches
1 conflict
0xc0077dc0…d81e
0x065c9d…c394
3 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x9fe89efe…278f
0x6f4756…dd5b
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
0x438cf5f603…8ef077
Audit this contract →
← previous block
·
next block →
recent activity