pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,959,900
← previous block
next block →
recent activity
Analyzing
Block #74,959,900
8 transactions · 7 stateful · 2026-05-16 11:40:04 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,959,900
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execute
#3
0x6c05cd2b
· blocks 1
#5
0x6a08580c
#6
setData
#7
0x30cb0e…9622
#4
0x5ddf3a9c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0002
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0xa74cd79c…705a
0x405b63…7777
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0xb4e825af…69e0
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:
Wrapped MON (WMON)
1 conflict on slot
0xbcc1b45913…43f94f
Audit this contract →
← previous block
·
next block →
recent activity