pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,077,519
← previous block
next block →
recent activity
Analyzing
Block #87,077,519
10 transactions · 8 stateful · 2026-07-11 15:05:19 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,077,519
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x38ae9ef8
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x6a525c27
#9
setData
#4
0x8f9ad8be
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x613560f2…8d9e
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b416
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x17f31bcc…45ee
0x928dc8…8207
2 touches
0 conflicts
0x17f31bcc…45ef
0x928dc8…8207
2 touches
0 conflicts
0x7c5567e4…87d0
0x928dc8…8207
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:
0x928dc8af…fd8207
1 conflict on slot
0x613560f2e4…f38d9e
Audit this contract →
← previous block
·
next block →
recent activity