pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,017,474
← previous block
next block →
recent activity
Analyzing
Block #91,017,474
12 transactions · 11 stateful · 2026-07-28 09:05:44 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,017,474
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x785f5745
#4
execFwdPositionOps
· blocks 1
#6
forward
#7
0x3f5c179b
#8
0x3f5c179b
#9
0x6a687160
#10
setData
#11
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9ba215a…1076
0x34b655…2a6f
4 touches
1 conflict
0x9e15e7b9…9fdf
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb1211028…6cda
0x0c65a0…0852
2 touches
0 conflicts
0x5860c4f3…0c39
0x3bd359…433a
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
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
0xe9ba215a64…9b1076
Audit this contract →
← previous block
·
next block →
recent activity