pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,777,141
← previous block
next block →
recent activity
Analyzing
Block #80,777,141
26 transactions · 18 stateful · 2026-06-12 10:30:29 UTC
Parallelism
88
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,777,141
· 26 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#3
execute302
#5
updatePrices
#6
0x6a2be03d
#7
0x6a2be03d
#8
0x5bf9264c
#9
0x5bf9264c
#10
0x98717539
#11
updateDataFeedsValuesPartial
#12
updateDataFeedsValuesPartial
#13
0x0f6795d9
#14
0x0f6795d9
#15
0xb24eec79
#16
0x3f5c179b
#18
forward
#19
forward
#20
forward
#21
forward
#22
setData
#23
0x5eeee2…a126
#24
0x39435dac
#25
0xc7e3ec2c
#2
0x0c7abd22
· blocks 1
#17
0x3f5c179b
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
17
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x1504aa7b…24ad
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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:
0x40c49f17…d22af0
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity