pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,281,119
← previous block
next block →
recent activity
Analyzing
Block #86,281,119
11 transactions · 11 stateful · 2026-07-07 22:21:20 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,281,119
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6943a490
#2
0x39435dac
· blocks 1
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x6a4d7c58
#7
0xd708c5d8
#8
setData
#9
0x39435dac
#10
0x5d2fd812
#3
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x140ee107…ea09
0x0a4fcb…a602
2 touches
0 conflicts
0x9665206b…5290
0x0a4fcb…a602
2 touches
0 conflicts
0xf0b7c5df…8f31
0x0a4fcb…a602
2 touches
0 conflicts
0xf0b7c5df…8f37
0x0a4fcb…a602
2 touches
0 conflicts
0xf0b7c5df…8f38
0x0a4fcb…a602
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
0xec0e022022…becb90
Audit this contract →
← previous block
·
next block →
recent activity