pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,264,014
← previous block
next block →
recent activity
Analyzing
Block #87,264,014
10 transactions · 8 stateful · 2026-07-12 11:52:47 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,264,014
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb89f9c…a906
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
updatePosition
#8
setData
#9
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb96a99db…95aa
0x34b655…2a6f
4 touches
1 conflict
0xe4b8f2c5…f54d
0x34b655…2a6f
4 touches
1 conflict
0x44d24653…fa2f
0x34b655…2a6f
4 touches
1 conflict
0x38b61269…48d7
0x34b655…2a6f
4 touches
1 conflict
0x0c366266…77e1
0x34b655…2a6f
2 touches
0 conflicts
0x169daa40…3f75
0x34b655…2a6f
2 touches
0 conflicts
0x355b2cf3…9b69
0x34b655…2a6f
2 touches
0 conflicts
0x508f9ae2…6bcf
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
0xb96a99db9e…4095aa
Audit this contract →
← previous block
·
next block →
recent activity