pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,580,533
← previous block
next block →
recent activity
Analyzing
Block #87,580,533
7 transactions · 6 stateful · 2026-07-13 23:10:17 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,580,533
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
setData
#4
0x0f6795d9
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
0xa5420e1f…3788
0x34b655…2a6f
4 touches
1 conflict
0xb920dba4…4826
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc577ef60…949a
0x34b655…2a6f
4 touches
1 conflict
0xcbdd47f9…7dcd
0x34b655…2a6f
4 touches
1 conflict
0xcbdd47f9…7dce
0x34b655…2a6f
4 touches
1 conflict
0x45e5059c…bcb1
0x34b655…2a6f
4 touches
1 conflict
0x461428a9…24b2
0x34b655…2a6f
4 touches
1 conflict
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
0xa5420e1f33…6e3788
Audit this contract →
← previous block
·
next block →
recent activity