pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,654,777
← previous block
next block →
recent activity
Analyzing
Block #80,654,777
9 transactions · 5 stateful · 2026-06-11 20:54:42 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,654,777
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
0x39435dac
#4
0x39435dac
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x6a2b210a
#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
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd12ab8ed…505a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xf6b1c2ec…f823
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad06
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
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
0xc0b9bd73c8…277f1c
Audit this contract →
← previous block
·
next block →
recent activity