pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,550,155
← previous block
next block →
recent activity
Analyzing
Block #80,550,155
12 transactions · 9 stateful · 2026-06-11 09:15:41 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
#80,550,155
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a2a7d35
#2
0x98717539
#3
permit2TransferAndMulticall
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
withdraw
#8
forward
#9
commit
#10
setData
#11
0xc7e3ec2c
#4
permit2TransferAndMulticall
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
0x802814d4…b323
0xaca92e…35da
4 touches
1 conflict
0xaeb46f64…7cfc
0xaca92e…35da
4 touches
1 conflict
0xbb02d03d…5383
0xaca92e…35da
4 touches
1 conflict
0xb1a0dd74…f087
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x5a1cd68f…4125
0x754704…b603
4 touches
1 conflict
0x25d30ad6…a8ec
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
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:
0xaca92e43…2435da
1 conflict on slot
0x802814d407…3cb323
Audit this contract →
← previous block
·
next block →
recent activity