pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,945,200
← previous block
next block →
recent activity
Analyzing
Block #86,945,200
12 transactions · 11 stateful · 2026-07-11 00:21:30 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
#86,945,200
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
withdraw
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#7
0x0f6795d9
#8
forward
#10
0x6a518d01
#11
setData
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06917e8…6985
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x2eac5688…c0eb
0x34b655…2a6f
2 touches
0 conflicts
0x3be33cca…0fff
0x34b655…2a6f
2 touches
0 conflicts
0x3be33cca…1000
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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:
Perpl
1 conflict on slot
0xb06917e887…5e6985
Audit this contract →
← previous block
·
next block →
recent activity