pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,011,280
← previous block
next block →
recent activity
Analyzing
Block #91,011,280
10 transactions · 10 stateful · 2026-07-28 08:34:33 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,011,280
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
executeBatch
#9
setData
#2
0xab083028
· blocks 1
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x05b171d5…87ed
0x065c9d…c394
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x79b1a1c2…e61c
0x065c9d…c394
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
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
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity