pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,047,744
← previous block
next block →
recent activity
Analyzing
Block #86,047,744
12 transactions · 11 stateful · 2026-07-06 20:23:35 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,047,744
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x39435dac
· blocks 2
#5
0x39435dac
· blocks 1
#8
forward
#9
claim
#10
setData
#11
0x39435dac
#6
0x0f6795d9
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc6e2e88…6569
0x34b655…2a6f
4 touches
1 conflict
0x179ead6b…f7f3
0x34b655…2a6f
4 touches
1 conflict
0x30fa662a…06e0
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
0x34b655…2a6f
4 touches
1 conflict
0xbefc4479…5cee
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
1 conflict on slot
0xcc6e2e88ab…f36569
Audit this contract →
← previous block
·
next block →
recent activity