pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,056,105
← previous block
next block →
recent activity
Analyzing
Block #86,056,105
12 transactions · 11 stateful · 2026-07-06 21:19:19 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
#86,056,105
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
0x6a4c1c4f
#4
0x0f6795d9
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
forward
#9
forward
#10
setData
#11
0x39435dac
#2
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1c3ae63a…7566
0x34b655…2a6f
2 touches
0 conflicts
0x25957369…c648
0x34b655…2a6f
2 touches
0 conflicts
0x3193444e…f0b2
0x34b655…2a6f
2 touches
0 conflicts
0x45856523…d213
0x34b655…2a6f
2 touches
0 conflicts
0x4fc45f65…d040
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
0xd800e635bc…14b1d7
Audit this contract →
← previous block
·
next block →
recent activity