pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,986,938
← previous block
next block →
recent activity
Analyzing
Block #75,986,938
9 transactions · 6 stateful · 2026-05-21 06:02:56 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,986,938
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#2
updatePriceFeedsIfNecessary
#3
executeBatch
#6
setData
#7
0x92a4c7…5dfb
#8
0x72127d…0c7c
#4
batchUpdate
· 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
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8c5b25f8…e1e3
0x065c9d…c394
4 touches
1 conflict
0x99a4e1eb…7f86
0x065c9d…c394
3 touches
1 conflict
0xfbb9e008…3165
0x065c9d…c394
3 touches
1 conflict
0xe395a198…85ae
0x065c9d…c394
3 touches
1 conflict
0x74a8ac9d…5eb1
0x065c9d…c394
3 touches
1 conflict
0xa17ec269…7cdd
0x1d1325…2305
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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity