pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,162,653
← previous block
next block →
recent activity
Analyzing
Block #91,162,653
10 transactions · 7 stateful · 2026-07-28 21:16:12 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,162,653
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#2
0xaf5e395a
#4
0x0c7abd22
#6
updateDataFeedsValuesPartial
#7
0x62be7533
#8
0x0f6795d9
#9
setData
#3
executePacked
· blocks 1
#5
0xb414539a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x275d1c2e…6781
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x969f2d28…4fa2
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
0x094452…0a09
2 touches
0 conflicts
0x00000000…0004
0x094452…0a09
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: Market-MON/USDC
3 conflicts on slot
0x275d1c2e75…cb6781
Audit this contract →
← previous block
·
next block →
recent activity