pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,962,236
← previous block
next block →
recent activity
Analyzing
Block #86,962,236
10 transactions · 8 stateful · 2026-07-11 02:15:18 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
#86,962,236
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x3f5c179b
#7
setData
#8
withdraw
#9
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x019a7c42…b604
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
2 touches
0 conflicts
0x1cbe4f94…3a9b
0x34b655…2a6f
2 touches
0 conflicts
0x232b0b19…d946
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0xfcdb591873…9e2b49
Audit this contract →
← previous block
·
next block →
recent activity