pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,437,881
← previous block
next block →
recent activity
Analyzing
Block #91,437,881
12 transactions · 9 stateful · 2026-07-29 20:23:06 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,437,881
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x4d8dc985
· blocks 1
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
#7
0x0f6795d9
#9
0x39435dac
#10
setData
#11
0x59558d29
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88f36c84…929d
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0422e0ce…38ba
0x34b655…2a6f
2 touches
0 conflicts
0x4d3eebe6…a3da
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x88f36c8497…00929d
Audit this contract →
← previous block
·
next block →
recent activity