pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,949,656
← previous block
next block →
recent activity
Analyzing
Block #75,949,656
9 transactions · 8 stateful · 2026-05-21 01:54:35 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,949,656
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
multicall
#4
updatePrices
#5
handleOps
#6
updateDataFeedsValuesPartial
#7
mint
#8
setData
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7609bf39…bbeb
0xa6afd3…d132
4 touches
1 conflict
0x15dfc675…c5e2
0xa6afd3…d132
4 touches
1 conflict
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0xff68ee4c…37e3
0x1111b3…4111
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
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:
0xa6afd386…b0d132
1 conflict on slot
0x7609bf394f…84bbeb
Audit this contract →
← previous block
·
next block →
recent activity