pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,406,307
← previous block
next block →
recent activity
Analyzing
Block #91,406,307
12 transactions · 12 stateful · 2026-07-29 17:43:10 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,406,307
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
executePacked
#3
0xab083028
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x39435dac
#8
transfer
#9
setData
#10
0x59558d29
#11
0xc7e3ec2c
#4
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0xae203c4f…309c
0x065c9d…c394
2 touches
0 conflicts
0x66de0ce3…337a
0x188d58…ea8e
2 touches
0 conflicts
0x66de0ce3…337c
0x188d58…ea8e
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
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity