pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,707,374
← previous block
next block →
recent activity
Analyzing
Block #80,707,374
8 transactions · 7 stateful · 2026-06-12 02:45:16 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,707,374
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
#5
0x3f5c179b
#6
0x39435dac
#7
setData
#2
0xab083028
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
0xe2263bea…6a9d
0x69df8a…6292
4 touches
1 conflict
0xed7dd7db…6022
0x69df8a…6292
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x5cc231f5…f1cd
0x69df8a…6292
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6aa0
0x69df8a…6292
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:
0x69df8a43…506292
1 conflict on slot
0xe2263beaa4…316a9d
Audit this contract →
← previous block
·
next block →
recent activity