pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,516,878
← previous block
next block →
recent activity
Analyzing
Block #75,516,878
9 transactions · 7 stateful · 2026-05-19 01:48:08 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,516,878
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
· blocks 1
#4
0x5bf9264c
#5
0x5bf9264c
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6e7600…e1f1
0xa6afd3…d132
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xe2e94dfa…5026
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdb9d8189…e926
0xa6afd3…d132
4 touches
1 conflict
0x2dc020c7…0697
0xc8689a…ee79
4 touches
1 conflict
0x10abefc9…c9bc
0x1d1325…2305
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
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:
0xa6afd386…b0d132
1 conflict on slot
0x3a6e7600b5…c1e1f1
Audit this contract →
← previous block
·
next block →
recent activity