pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,090,235
← previous block
next block →
recent activity
Analyzing
Block #91,090,235
19 transactions · 12 stateful · 2026-07-28 15:11:53 UTC
Parallelism
89
/100
Blocked
8
%
Avg conflicts / tx
0.05
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,090,235
· 19 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#2
updatePrices
#3
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
execute
#10
updateDataFeedsValuesPartial
#11
executeBatch
#12
execFwdPositionOps
#13
0x3f5c179b
#14
batchUpdate
#15
forward
#16
setData
#17
execOrders
#18
0x59558d29
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
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
0x34d5be38…1100
0x6f7e11…3d7e
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x58733c38…f2cd
0xe52b14…7230
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