pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,333,058
← previous block
next block →
recent activity
Analyzing
Block #84,333,058
12 transactions · 9 stateful · 2026-06-28 21:52:39 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,333,058
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x42bbae7a
#4
forward
#5
forward
#6
0x0f6795d9
#7
setData
#8
0x914c1b…8691
#9
0x3fdf8d…298e
#11
0xc7e3ec2c
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d3fc79…df78
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0xb1a0dd74…f087
0x188d58…ea8e
2 touches
0 conflicts
0x0b76d19c…bf9a
0x34b655…2a6f
2 touches
0 conflicts
0x13d7018d…ff79
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
0x98d3fc7978…b0df78
Audit this contract →
← previous block
·
next block →
recent activity