pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,936,678
← previous block
next block →
recent activity
Analyzing
Block #75,936,678
9 transactions · 7 stateful · 2026-05-21 00:28:09 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,936,678
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x40e7e2…0dd6
#2
0x0c7abd22
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
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13f1eda2…58ce
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x81517508…299c
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
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:
Perpl: Settlement / Helper
1 conflict on slot
0x1fff6dcbfb…92b3f4
Audit this contract →
← previous block
·
next block →
recent activity