pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,294,855
← previous block
next block →
recent activity
Analyzing
Block #87,294,855
9 transactions · 8 stateful · 2026-07-12 15:19:02 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,294,855
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
#7
0x6a53b0de
#8
setData
#4
0xed82b078
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
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21b9ccc3…8a89
0x065c9d…c394
4 touches
1 conflict
0x4381754b…f3f6
0x065c9d…c394
4 touches
1 conflict
0x659aa528…522a
0x065c9d…c394
3 touches
1 conflict
0x81428b6c…81df
0x065c9d…c394
3 touches
1 conflict
0x347327ff…3863
0x34b655…2a6f
2 touches
0 conflicts
0x4caf91f9…8ab5
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xce827910a4…82ff22
Audit this contract →
← previous block
·
next block →
recent activity