pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,045,633
← previous block
next block →
recent activity
Analyzing
Block #84,045,633
9 transactions · 7 stateful · 2026-06-27 13:58:09 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,045,633
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0xed82b078
#6
exactInputSingle
#7
0x6a3fd769
#8
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x179fd795…fbe5
0x34b655…2a6f
3 touches
1 conflict
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x31658946…5d47
0x34b655…2a6f
2 touches
0 conflicts
0x353887b1…18ef
0x34b655…2a6f
2 touches
0 conflicts
0x49194594…2c70
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
1 conflict on slot
0x408e66bba7…d43d6b
Audit this contract →
← previous block
·
next block →
recent activity