pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,243,229
← previous block
next block →
recent activity
Analyzing
Block #91,243,229
12 transactions · 11 stateful · 2026-07-29 04:01:31 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,243,229
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
· blocks 1
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a697b93
#10
setData
#11
execOrders
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x04f6d949…d859
0x34b655…2a6f
2 touches
0 conflicts
0x12b73161…a4ad
0x34b655…2a6f
2 touches
0 conflicts
0x2406ccf7…c1cb
0x34b655…2a6f
2 touches
0 conflicts
0x27dd8ebd…6d57
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:
0x48cba278…e2b48b
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity