pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,385,890
← previous block
next block →
recent activity
Analyzing
Block #91,385,890
13 transactions · 9 stateful · 2026-07-29 16:00:17 UTC
Parallelism
85
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,385,890
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x29eed2d3
#7
0x0f6795d9
· blocks 1
#9
0x0f6795d9
#10
setData
#11
0x59558d29
· blocks 1
#8
0x0f6795d9
#12
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
2 touches
0 conflicts
0x3380de39…89c7
0x754704…b603
2 touches
0 conflicts
0xab35ca26…1e80
0x754704…b603
2 touches
0 conflicts
0xe8d7d37b…4ece
0x754704…b603
2 touches
0 conflicts
0x12cbc8ba…bd5e
0x99c7a7…8bf0
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity