pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,232,368
← previous block
next block →
recent activity
Analyzing
Block #75,232,368
10 transactions · 6 stateful · 2026-05-17 17:59:29 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,232,368
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x669a7d5e
· blocks 1
#3
updateDataFeedsValuesPartial
#4
commit
#5
0x6a0a0279
#6
0xe23417…aae2
#7
0x073c37…e569
#8
setData
#9
0x39435dac
#2
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb643582…2626
0x3bd359…433a
4 touches
1 conflict
0xb0339ea9…b02e
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x878750…1e52
4 touches
1 conflict
0x00000000…0002
0x878750…1e52
4 touches
1 conflict
0x00000000…0003
0x878750…1e52
4 touches
1 conflict
0x0bcaba7e…0e80
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0xf8127de7…d5ec
0x3bd359…433a
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:
0x3bd359c1…15433a
1 conflict on slot
0xcb643582c0…392626
Audit this contract →
← previous block
·
next block →
recent activity