pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,550,409
← previous block
next block →
recent activity
Analyzing
Block #80,550,409
11 transactions · 9 stateful · 2026-06-11 09:17:23 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,550,409
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x785f5745
· blocks 1
#6
0x6a2a7d9a
#7
0x32366535
#9
0x39435dac
#10
0xc7e3ec2c
#8
0x785f5745
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
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:
0x0c65a0bc…0e0852
1 conflict on slot
0x490911ccd2…a15fea
Audit this contract →
← previous block
·
next block →
recent activity