pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,679,613
← previous block
next block →
recent activity
Analyzing
Block #75,679,613
9 transactions · 8 stateful · 2026-05-19 19:55:25 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,679,613
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
_makeSwaps
· blocks 2
#4
cancel
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#2
0xab083028
· blocks 1
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x5cb3e984…7f98
0xa6afd3…d132
3 touches
1 conflict
0x52e291f4…7b5f
0x000000…8ba3
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000d
0x2b37ef…0bdc
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:
0x2a68ba18…8e90c5
3 conflicts on slot
0x99a2130578…57dffc
Audit this contract →
← previous block
·
next block →
recent activity