pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,502,228
← previous block
next block →
recent activity
Analyzing
Block #75,502,228
9 transactions · 8 stateful · 2026-05-19 00:07:46 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,502,228
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updateDataFeedsValuesPartial
#3
0xbc55ae21
#4
addLiquidity
· blocks 1
#5
0x5bf9264c
#7
0x6a0baa4a
#8
setData
#6
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x5d685379…947f
0x5afd3e…7620
2 touches
0 conflicts
0x7e5f8ac8…6074
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x3378e8b6…20a9
0x754704…b603
2 touches
0 conflicts
0x988c1266…7630
0x754704…b603
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:
0x754704bc…afb603
1 conflict on slot
0x4039b31fcf…cb0f4a
Audit this contract →
← previous block
·
next block →
recent activity