pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,555,383
← previous block
next block →
recent activity
Analyzing
Block #75,555,383
9 transactions · 8 stateful · 2026-05-19 06:05:48 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,555,383
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
· blocks 2
#2
0xbb5d006a
#3
updateDataFeedsValuesPartial
#6
0x98717539
#7
0x6a0bfe34
#8
setData
#4
0x0d484c28
#5
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b703c6e…4494
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x5f999d80…4e25
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x586dcd47…ab7a
0x0594c7…a3be
2 touches
0 conflicts
0x785ef18f…53eb
0x0594c7…a3be
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x4b703c6e2b…5e4494
Audit this contract →
← previous block
·
next block →
recent activity