pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,350,375
← previous block
next block →
recent activity
Analyzing
Block #84,350,375
9 transactions · 7 stateful · 2026-06-28 23:48:04 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,350,375
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#6
0x9e76c652
#7
setData
#8
0x39435dac
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x1edd9a58…608f
0x34b655…2a6f
2 touches
0 conflicts
0x29a8d47a…de9f
0x34b655…2a6f
2 touches
0 conflicts
0x2d69c1bb…6b5e
0x34b655…2a6f
2 touches
0 conflicts
0x67fc285e…2584
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
3 conflicts on slot
0x8e739938fe…14e7ab
Audit this contract →
← previous block
·
next block →
recent activity