pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,133,020
← previous block
next block →
recent activity
Analyzing
Block #87,133,020
10 transactions · 9 stateful · 2026-07-11 21:16:09 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,133,020
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 3
#6
setData
#9
0x39435dac
#5
0x0f6795d9
· blocks 1
#7
0x0f6795d9
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x03faff26…f533
0x34b655…2a6f
6 touches
3 conflicts
0x04ac0a0c…6be2
0x34b655…2a6f
4 touches
1 conflict
0xfc2493d3…6898
0x34b655…2a6f
4 touches
1 conflict
0x04ac0a0c…6be1
0x34b655…2a6f
4 touches
1 conflict
0xe2406397…37cc
0x34b655…2a6f
4 touches
1 conflict
0xf2e22c06…42d6
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity