pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,333,370
← previous block
next block →
recent activity
Analyzing
Block #87,333,370
12 transactions · 11 stateful · 2026-07-12 19:36:34 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
#87,333,370
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0xc5a04723
#8
handleOps
#9
0x6a53ed3a
#10
setData
#11
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1a51db3…eba8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x02845d2c…91be
0x34b655…2a6f
2 touches
0 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
2 touches
0 conflicts
0x1946f20a…ac91
0x34b655…2a6f
2 touches
0 conflicts
0x19503eb9…33d1
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
0xa1a51db3c3…07eba8
Audit this contract →
← previous block
·
next block →
recent activity