pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,346,588
← previous block
next block →
recent activity
Analyzing
Block #74,346,588
8 transactions · 7 stateful · 2026-05-13 15:23:13 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,346,588
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
approve
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#3
swap
· blocks 1
#4
0x39ecce49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00c46468…f328
0x3bd359…433a
4 touches
1 conflict
0xce2b6650…ecc3
0x5c2513…7777
4 touches
1 conflict
0x00000000…0000
0xcc67aa…c71c
4 touches
1 conflict
0x00000000…0003
0xcc67aa…c71c
4 touches
1 conflict
0x07fd78a9…e743
0x065c9d…c394
2 touches
0 conflicts
0x158828b7…941e
0x065c9d…c394
2 touches
0 conflicts
0x54b436f6…1e71
0x065c9d…c394
2 touches
0 conflicts
0x80629aca…a1a1
0x065c9d…c394
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:
Wrapped MON (WMON)
1 conflict on slot
0x00c46468d1…54f328
Audit this contract →
← previous block
·
next block →
recent activity